Hi,
Currently we created a project inside JIRA, called = Release. This project manages all releases for our company. Our workflow is quite simple Draft - In progress - Merged - Ready for Deployment - Done. we do have several components that we release. They are interrelated. Our release workflow would need some improvement.
Can I be able to customise JIRA so that it would not be able to proceed a Release ticket, to Ready for Deployment if an existing ticket is still pending with the same status and with the same component. Meaning for Release project, it would be impossible to create two tickets with Ready for Deployment status, and for the same component.
Further I could possibly configure the project to add another identifier just to add to that validation. :)
Thanks in advance and more power!
Hi,
did you think about creating dependencies / links between tickets. You might know that you can create subtasks for an issue. But you can also have a super issue which contains links to other deployment/release issues. This can be done by some automation apps (Automation for Jira, Scriptrunner & many others). You could then define rules, disabling a status change to Ready for Deployment, if any of the child issues are not completed.
There still needs to be some logic applied somewhere, but you get the idea, that dependencies between issues make things easier as you can run some JQL queries on child issues.
Best
JP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.