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; } } }

Keep Released tickets in their status and view them as Done

Silvia Saric

Hello,

We have a status called "Released". In our workflow, there are no transitions out of there which is good. However, when I click on an issue, it is possible anyway to transition it from Released to Done or Closed. I would like to remove that possibility. Also, every time we want to release tickets, we get a warning message that the issues are not "done" which they are. So I guess this question regards two things: How to make our Released status be valid as a Done status and remove any transitions out of there.

Thanks in advance,
Silvia

Accepted answers

All comments

Nikola Perisic

Hello @Silvia Saric

Are you on the Kanban or Scrum board? For Kanban boards, issues need to be done in order for them to be released. As for you seeing the additional transitions, there might be a condition that allows only specific users to see this transition - other than that, I don't have another explanation.

Silvia Saric

Hello @Nikola Perisic

We are on Kanban. Every time we release tickets we just skip the part alerting that the issues are not done and release them anyway. Their status "Released" remains then which is good. The problem is that the Reporters usually think that we expect them to mark the issue as Done once they have validated it in Production - this is not what we want. Therefore, I am searching for a way to keep the issue in Released status - or at least restrict the Reporters from transitioning issues.

Nikola Perisic

@Silvia Saric you can restrict the reporters from transitioning the issues by applying a condition on your workflow. Before that, you would create a group of people that are excluding those who need to be restricted. Then for that transition you would choose Users In Group option - only the users in that group will be able to do the transition, others will not.

Silvia Saric

@Nikola Perisic Is it possible to restrict only the issue Reporter instead of an entire group?

jeff_trotman

Maybe this will help,

You want to consider the Released as Done, change it in your workflow from Blue(any type of in progress, released, building, in review status) to a new status called Released, but with Green (any type of done, cancelled, completed status).

Only allow it a transition in, from one of the previous statuses, then it will have no way out, unless, you have any status which allows transition from any.

Silvia Saric

@jeff_trotman Thanks for your input! Can you please check the screenshots I sent to Nikola Perisic here? The Released is already Green, so that is according to what you suggested, right?

jeff_trotman

Yes, that means it is considered a done status.

I'm curious who should be allowed to move it to Released, if you click on the transition itself, not the status, you can set up rules there to say who can and cannot transition to the status.

jeff_trotman

Also, do you want the resolution marked as done? that's different to status.

You can also set resolution in the rules area for the transition.

Silvia Saric

@Nikola Perisic @jeff_trotman I figured it out guys! Thanks to one of your comments that led me on track, Jeff. The entire workflow was really a mess, so I created a new one based on it. When I went through each status one by one, it became clear that whoever made the original left some things unfinished or unhandled. I changed the resolution to the default status Done now, so I will verify after our release on Thursday if all went well. The above has solved the case of making Released the final status anyway. Thanks a lot for all your kind help, all the best to you.

jeff_trotman

Good to hear @Silvia Saricdo you need help with moving the old releases to resolution Done or are you good to go alone on that?

Silvia Saric

@jeff_trotman At this point, I am uncertain if I even have to move them. Maybe it is better to start fresh starting with tomorrow's release. I tried with one test issue and it worked like a charm. The resolution switched to Done and the comment was automatically posted, tagging the stakeholder to urge them to verify in Production. Also, that is the end status, no way out to transition anywhere after Released. I also added the Done resolution to the Done status (that we use for configuration issues that are in no need of code changes) and renamed the Won't Do status to Scrapped for Closed issues that are no longer necessary. That was my goal with this question here so I am happy with the help I got from you guys, thank you.

jeff_trotman

No problem, glad to have helped.

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

cloud

jira-cloud