every time my organization is about to release a version a slow manually & painful process starts when 3 different Heads of department need to sign off (each) release before I as a Jira admin can release it from the release candidate pull.
Does anyone have a suggestion on how to automotive this flow?
I've built a dashboard and every release had hundreds of items so I need a simple and overall solution to all of the release package and not each ticket individually.
I'm using the Jira cloud server - I would be happy to hear any suggestions!
What about creating a task for every release that has three approval sub-tasks assigned to each dept head? Use automation (addon for server) if you want to notify you when all sub-tasks are complete or something similar. You might even not assign the tasks to the dept heads until you are ready to release. Of course some of this depends on the details of your process, e.g. what do the dept heads assess to approve/reject.
I guess adding a manual ticket is plausible but I was aiming for something more automated that won't create any more tickets to the hundreds we already have in each release.
anyways I was thinking big, something like:
Automation: send manager 1 a week before the release due date email to push a button that this version is verified on he's behalf - and a count down clock that ends 4 days (after the email was sent)
After this button was pushed by manager 1 - content gets freezer for this release and manager #2 receives a message that he has 2 days to verify and push a verification butten
There are solutions available from marketplace like Group Sign Off and others which are capable of a broad range of such feature - but I cannot say for sure if every aspect of your requirement can be met (I haven't tested it).
Most likely you would be able to implement parts with it, and garnish your process with some Automation rules.
Especially for the due dates / countdown I am not sure if this can be done out of the box.
As always - the recommendation would be to start small and to add features as first success is visible with the one or another solution you want to go with.
I think you'd use a ticket to represent a release like Jack suggested with addition of Jira Automation on top (https://www.atlassian.com/software/jira/features/automation)
If you had:
Then set up a bunch of rules:
Rule 1: Trigger initial email
issuetype = Release AND status = Pending AND "Release due date" > 7d
Rule 2: Trigger verification
Hope that helps
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event