Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,204
Community Members
 
Community Events
176
Community Groups

Issue crossed out

Hi all,

 

I have question, As per my understand normally issue crossed out, when the issue in done status also resolution is done and someone opened the issue to any other status it will crossed out.

but here my question is when the issue went to done status with resolution is done, will the issue is crossed out? or only the issue moved to any other status then only it will crossed out?

some one please clarify.

 

Thanks,

Srinivas

1 answer

1 vote

No, that's not right.

An issue is crossed out when it is resolved.  That is just when the resolution field has a value (and it does not matter what that value is called).  Unresolved issues have an empty resolution.

Status is irrelevant.  

But, you do need to think about it in your workflows - you need to define which status you want the system to consider resolved, and then

  • Set it with a post function, or ask the user for a value, when you transition into any of your "closed" status
  • Clear it with a post function when you move out of any of the "closed" status into any "open" one

I think you've missed the second one - an issue got resolved, then you re-opened it, but because you didn't clear the resolution, it's still resolved.

Hi Nic,

 

Thanks for your clarification, here my extended question is when the issue issue done and also resolution done ( all transitions using for statuses, resolution post function implemented on done transition) but it not crossed out, showing plain in backlog once that issue moved to any other status then only it will crossed out (there is no resolution clearance)

what is reason behind the issue not crossed out when the issue meet resolution and status is done on the first time.?

Thanks

Srinivas

Like Tyrone Herring likes this

Two possible reasons

1.  You haven't actually set a resolution - a lot of people new to this consider only one of the transitions and don't look at the edge cases where things move into a status via a less-used transition.  Usually happens when there is an "all" transition that is right, but another one has been added for some reason - users will see both transitions and may use the one that does not have the "set resolution" function on it.

2. Some places don't report the strike-out because it's not important.

There is another problem here though - why are you getting resolved issues in your backlog?  A backlog is for planning open issues, but, by definition, resolved issues are done, so they should not be in the backlog.  Or another way to put it - you shouldn't see strikeouts in your backlog, because the issues are done, and backlogs shouldn't include done issues.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events