https://confluence.atlassian.com/jirakb/using-jira-for-change-management-193300032.html
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.
Thanks,
Suresh
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:
Hi Timothy. Thanks for your reply. Very helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.