Strikethrough when Issue moved to Next Sprint Backlog

[Jose Manuel Fernandez]

Hi everyone,

I have read many articles about the problem with the strikethrough on issues when moved between states. This issue is linked to the Resolution and I fixed it clearing the resolution in the transitions of the workflow. I don't have any problem when I'm moving issues from state to state in the current sprint board.

The problem I have is when moving Issues to the Next Sprint Backlog (and sometimes to the Backlog). There is no transition in the workflow that I can fix this resolution when moving items to the next sprint backlog.

How can I fix this strikethrough in this case?

Thanks in advance

[Jack Brickey]

The strikethrough as you mentioned is associated with the resolution field. Simply put once an issue is resolved, which equates to any value in the resolution field, then the issue has a strike through. If you ever re-open an issue you must ensure that you clear the resolution field. You do this in CMP projects via a post function on the transitions out of the appropriate done status. If you have issues that already have the strikethrough that are not in a done status then consider using the bulk edit and clear the field.

[Jose Manuel Fernandez]

Thanks @Jack Brickey (very cool emoji for this time of the year). I know what you mean, but I can't find how to clear the resolution for items that are in the backlog and I move them to the Next Sprint Backlog (in the backlog view, without having the sprint started)... I don't find any transition saying "From Backlog to Next Sprint Backlog"...

All the rest actions and transitions are fine. I created the post function for every transition (except when it's Done). For instance, when I create a new Issue and set it to the Backlog when I move an Issue from the Backlog to other states in the Sprint (To do, in progress, in review, etc.) is fine because I'm clearing the resolution at every transition...

Any idea?

[Jack Brickey]

So if your workflow is well formed (see end of post), where the Resolution is concerned, then you don’t need, or want really, to have a PF to clear the Resolution on transitions from any status except where the resolution has been set. In other words, if it isn’t set you don’t need to clear it. 

Now if you have issues in a status where the status Category is either To Do or In Progress and the resolution is set then this is an error condition and you should clean all of these up. If you use the below JQL and find any results then you should go thru each one and clear the Resolution field.

Project = xxx and statusCategory != done and resolution is not empty

A well formed workflow…

• set the Resolution anytime you enter a done category status. There are exceptions to this, the most common is where you have a two step closure workflow, e.g. developer sets an issue to Resolved and the customer sets it to Closed. In this scenario it is common to only set the Resolution on the transition to Closed.
• clear the resolution anytime you exit a done category status