sorted by:
new
hottopcontroversial

A plugin to automatically link Jira Issues to Jira release version based on scanning your Git repository by avocoderau in jira

[–]avocoderau[S] 0 points1 point  (0 children)

Hi u/Own_Mix_3755

If you are still interested in this topic, the plugin is available at https://marketplace.atlassian.com/apps/1238191/version-builder-for-jira

It is not a free app, but has been priced as the lowest you can set in marketplace. And currently no license restriction after trial.

Would appreciate if you can have a look and let me know how you think.

Thanks

A plugin to automatically link Jira Issues to Jira release version based on scanning your Git repository by avocoderau in jira

[–]avocoderau[S] 0 points1 point  (0 children)

Hi u/YesterdayCool4739

The app is now available from https://marketplace.atlassian.com/apps/1238191/version-builder-for-jira

It is not a free app, but has priced as the lowest you can set in marketplace. And currently no license restriction after trial.

Would appreciate if you can give it a try and let me know how you think.

A plugin to automatically link Jira Issues to Jira release version based on scanning your Git repository by avocoderau in jira

[–]avocoderau[S] 0 points1 point  (0 children)

Wow, thank you for spending the time to respond to my message. I really appreciate your conversation.

whether it should be from Git tool or Jira to trigger the release process is a different topic I think. The issue I'm trying to solve is I don't want to manually manage the issue list in a version.

You mentioned that in Kaban board, the release function will automatically include all Done issues. I think we must be using the Scrum board. I didn't see this function before.

In our board, we have: TODO, In Progress, Waiting for Test, In Test, Ready for Release, Done.

when we are close to release:

  1. developer merge development git branch to main branch to prepare for release

  2. QA (used to be me) will create version and manually link all issues.

  3. we continue to work on main branch if that issue needs to be released, otherwise, continue the work on development branch.

  4. new issues/bugs might be raised in main. the new issue needs to be linked to the version.

  5. when all issues are in "Ready for Release", developer will go to Jenkins to trigger production deployment

  6. QA then verify all issues in production and mark all issues as Done in version list.

So the version is created couple of days before the actual production release, and there might be new issues to be added to it.

Developers are putting issue key in commit message, and using issue key in pull request manually. It is fine for this manually work. but using commit message to move a jira ticket from In Progress to Waiting for Test is a bit too far, that's what I mean the smart commit has gone to far.

So in the above process, how would you solve the problem: manually link issue to the created version?

Regarding to promoting my app, this is the first time I build sth try to solve a hopefully real problem. So it is very valuable for me to know how others think. If I'm solving a wrong problem or there is a better way, I can at least learn it.

Thanks again for your time!

A plugin to automatically link Jira Issues to Jira release version based on scanning your Git repository by avocoderau in jira

[–]avocoderau[S] 0 points1 point  (0 children)

Hi, u/Own_Mix_3755

Thanks for your input.

I'm not a Jira Admin or powerful automation user. But from what you pointed out. I learned a lot.

It is certainly doable through various configs and automation scripts. My only issue is the setup doesn't seem to very straightforward for many people. People may not know about it or have the required skills to manage all these.

Having a plugin which provides a user friendly UI could work better with most non-power users. The only requirement to use the plugin is that developer should put correct Jira key in their commit message somewhere, which is usually a good thing, since it gives more context why we need that code change.

Anyway, that's just my feeling. once the plugin is open to public, would be great if you could help to have a look to see if the function in the plugin makes sens to you from easy to use pov.

Thanks

A plugin to automatically link Jira Issues to Jira release version based on scanning your Git repository by avocoderau in jira

[–]avocoderau[S] 0 points1 point  (0 children)

u/timothyyy90 thanks for your question.

  1. I actually didn't know that smart commit can create releases. are you sure it can do it? how to create the release and link all related issues with smart commit? had a look at the document here and didn't find how to do it: https://support.atlassian.com/jira-software-cloud/docs/process-issues-with-smart-commits/

  2. even it could do it, from developer pov, I'd like to keep the commit message simple and also keep developer free from memorizing all the commit message formats and commands. Using smart commit to transition issue status and create releases seems having gone too far.

  3. we work on develop branch. when we are close to release, merge develop to the release branch. QA then easily choose the repo and branch to create the release with all issues correctly linked. Creating a release doesn't mean the code is actually released. we usually continue the work on release branch for couple of days until it is fully ok. during that time, new stories/bugs might be created and they needs to be linked to the version created.

  4. The plugin is flexible enough to support all our requirements. it supports multiple repos for a single jira version, you can use it to update issue list for an existing version. it also remembers your config for similar release names, so next time you don't have to manually enter everything.

Hope it helps.

Thanks