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

[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]

@jeff_trotman 
So this is the transition itself (to Released):

Yes, I want the resolution marked as done (without the status actually being called Done). We have two "done resolutions" in practice - One is Done (configured tickets), the other is Released (code released in fix version).

Finally, I want Released issues to remain in their status, not risking anyone to transition it to something else.

[jeff_trotman]

ok, first off you would need to create a new resolution, you can do this in Settings -> Work Items -> Resolutions.

Once done, if you edit the transition - perform actions - update an issue field - select resolution, if you have added Released to your resolutions, it will appear here and you can select it.

[Silvia Saric]

@jeff_trotman So this will at least solve the situation with the issue being marked as "Unresolved" even though it has been Released, right? Follow-up question to that, why did I have to add a custom one like that, would it not be enough to use the default Done?

1: Added the bottom item (Resolved)



2. Added it to the Post Functions of the transition from Ready for Release to Released:

[jeff_trotman]

Yes, now the unresolved work issues, will automatically become Resolved, once transitioned to Released.

You could have used done, but you mentioned you didn't want it as done, also it becomes a lot easier to filter, if you use a resolution that is different to done.

[Silvia Saric]

@jeff_trotman I did not want the status to be Done, but resolution could be whatever besides Unresolved I guess. But like you said, maybe it is good to keep them separated. This will only affect new released tickets right? Old released tickets are still marked as Unresolved now. The main issue remains now though - how to prevent further transitioning from Released to Done/Closed that still seems to be possible.

[jeff_trotman]

Yes, it will only affect new issues, you can force the change through bulk edit, by transitioning the old issues from released to released, that will update the resolution.

Once the resolution is marked as resolved, it is the equivalent of closing the issue, so unless you allow transitions from closed or resolved, or allow them to be re-opened, they won't move anywhere.

[Silvia Saric]

@jeff_trotman I tried transitioning an old Released issue to Done, then all the way through the flow back to Released again - but it still states it as Unresolved. Maybe I did it the wrong way?

[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?

[Nikola Perisic]

@Silvia Saric 

You can refer to this page: https://community.atlassian.com/forums/Jira-questions/How-to-prevent-the-Reporter-from-transitioning-an-issue-using/qaq-p/2604819

Also, for the condition there is to ALLOW only Reporters to do the transition. There is an app called JWME that allows you to add more conditions to it, but it's paid.

[Silvia Saric]

@Nikola Perisic The first obstacle is still this:

Workflow ends with "Released:

Yet, anyone can transition the issue within it to this (plus it says "Unresolved" which is not true according to our way of work):

So, I do not know where to edit the conditions.

[Nikola Perisic]

@Silvia Saric 

When you click on the view workflow, does it lead to the same workflow from the image above?

[Silvia Saric]

@Nikola Perisic Yes, same workflow.

[Nikola Perisic]

@Silvia Saric 

I am following the conversation that you are having with Jeff as well. It seems that the resolution was removed.

[Silvia Saric]

@Nikola Perisic @jeff_trotman We are having a proper release this Thursday. I can report back here then after seeing how it behaves now. When I tried transitioning an old released issue throughout the flow, after having added the new Resolved resolution, it still ended up as Unresolved - but perhaps that won't happen with new issues that have not been Released previously.

[jeff_trotman]

@Nikola Perisic From what i can tell, Silvia is talking about one of her old Released issues, which didn't have the resolution populated.

@Silvia Saric I misspoke with my original solution to populating the old issues, it might be more work than you would want to contemplate. The forums are stating i have some html in my full answer, so when it allows me, i will give a full explanation.