nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to create automation for ready to deploy board into On Hold

Muhammad Rafly Andrianza

Hello, Atlassian Team

My team wants to create an automation for our jira board movement, when the issue has arrived from QA & UI REVIEW into READY TO DEPLOY it will automatically move to ON HOLD board. With notes the issue have another linked issue that still in transition before READY TO DEPLOY (or still in progress), as we know that we separated our issue between FE side and BE side and when they come to integrate in production, both issue need in READY TO DEPLOY board before we can move the issue into our QA PROD TEST together.

Thanks, I hope I can get answer for this.

SOP Documentation-Jira Board Workflows (2).png

Accepted answers

Alex Koxaras -Relational-

Hi @Muhammad Rafly Andrianza and welcome to the community,

There isn't a clear answer to your question since you don't move issues to boards, if the boards are on the same project. You move issues to different jira projects (containers). With that said and assuming that you have the boards on the same project you have only to map the "Ready to Deploy" status to the desirable column on your "On Hold" board.

If the above it's not the case, since judging from your workflow you attached here it seems that on Hold is another status, kindly provide more clear details as how you want this to work.

All comments

Alex Koxaras -Relational-

Hi @Muhammad Rafly Andrianza and welcome to the community,

If the above it's not the case, since judging from your workflow you attached here it seems that on Hold is another status, kindly provide more clear details as how you want this to work.

Muhammad Rafly Andrianza

Yes, I mean my team wants to implement Jira Automation with rules that when Issue A move into Ready to Deploy but the Issue A have linked issue with Issue B that is in progress, so the Issue A will be move automatically in to On Hold till the Issue B are in Ready to Deploy,and Issue A will be return to Ready to Deploy again.

Muhammad Rafly Andrianza

Hello, is there any reply updates for this question?

Alex Koxaras -Relational-

Hi @Muhammad Rafly Andrianza

I understand your requirement, but I don't agree with it, because it will take a long time to execute and most likely you might hit the service limits quickly, and the UX will not be good. Your rule would be (because I tried to create it) something like the following:

Trigger on issue transition to "Ready to deploy"
Condition to check if issue type is appropriate (e.g. task)
You lookupissues for an appropriate JQL to find if linked issues exist on "In Progress" status
Create smart variable (optional) to store lookupissue size
Compare the above variable to be greater than 0. If that is valid then
Transition the issue to "On Hold" status

That would work well for the first part only. But for the issues to return back you would have to amend the above rule to include IF/ELSE component to get them back. And then you would have to add conditions from the "On Hold" status, so that the users can't move the issue from there, unless it's an automation.

To me the above is a bit wrong approach. Instead of doing that I would change the workflow a bit. I would have an extra status (not named On Hold) called e.g. Deploying. After all issues finished working and were ready to be deployed, then the user should move them to "Ready to deploy". Then the user who is responsible for the deployment should transition the issue to deploying if he/she had to work with it. BUT, on that specific transition, and within the workflow you would add a validator NOT to allow the specific transition to happen if related issues existed on previous statuses.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

board

automation