Hi all,
The organization I'm working with is leveraging Jira for it's Change Management practice and as part of a continuous improvement initiative, would like to establish a standard change catalogue to reduce the overhead associated with tracking and approving low-risk, high-frequency changes that have a solid track record of not causing incidents.
Here's the working idea...
A new issue type is created under the "Change Request" project with a form that developers can complete and submit to have a change that meets the criteria above to be considered a standard change. Once submitted, the CAB would review and ultimately approve or deny the request.
Is there a way to have other Issue Types under the same "Change Request" project reference each other? Here's an example of the use case... "Application" is one of the existing issue types under the "Change Request" project. Could we add a drop-down field to the "Application" form which could be dynamically populated with approved Standard Changes from the newly created Standard Change issue type?
Apologies if this is already documented somewhere - I looked around the forum for a similar inquiry but couldn't find one. I'm not a regular Jira user either, so please let me know if any additional clarification is needed, or if someone has a better idea to accomplish what we're after.
Thanks in advance!
Jeremy
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.