The link above describes how JIRA can be used for change management using a new issue type called 'Change Request'. This workflow covers the workflow from a change management perspective.
ie: Request Open, Request Closed, Under Review, Reopen Request, Under Assessment, Awaiting Approval, Implementing Change, Monitoring Change, Reviewing Complete.
How can I take an approved Change Request and put it through a 'Change' lifecycle i.e; (for example) Requirements Analysis, Development, Testing, Sign-off and Implementation? Would like to maintain the link/traceability to the 'Change Request' & ensure the 'Change Request' Requestor has visibility of which stage within the 'Change' lifecycle it is.
There are a few ways that you can do this.
One way is to create the Change issue type as a subtask and associate it with the Change Request issue.
You can also have a Change issue linked to the Change Request via an issue link.
Or you could use something like Structure for a hierarchy:
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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