We start evaluating JIRA Software for Release Management Tool and looking for a good pracitice sample workflow that support for product release for multiple Environments (QA/UAT/PROD) on different regions/clients.
The current setup we have in JIRA is that we have a project call "Release Management". Whenever user submit a deployment request, they will create a RFC ticket in that project. Under that standard task, user can create different types of work order (as subtask) such as a deployment request, server change request, network change request, etc... Therefore, RFC and work order are parent/child relationship. They both will have separate workflow.
So at DOOR meeting, they will approve RFC. However, different operation teams will use Work Request that assign to their team to execute the change.
So, is there a good practice of workflow in JIRA which can do something like this.?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs