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,456,891
Community Members
 
Community Events
176
Community Groups

Strike out

Edited

I am getting the issue type getting strike out any time the issue moved from  the new status to in Progress status. 

On the create issue transition for bug issue type  , I have created a post function  to change the resolution to  To Do. However it is not doing it and its still showing it as un resolved. But this is not happening if the issue is in In progress state. Could you please help with he strike out issue so that  the issue is not strike out .

 

 

Capture 2.PNG

2 answers

1 vote

You need to stop doing this, you've misunderstood what the resolution field is for.

The resolution field has two broad states - 

  • Empty - the issue is unresolved and needs more attention
  • Filled (with any value at all) - the issue is resolved and will be seen as complete by most of the reporting in Jira (including putting the strike-through on it)

Your resolution of "to do" does not make sense - you're telling Jira the issue is resolved, but the users that it is both resolved and not at the same time.

Get rid of your to-do resolution (and any others that do not mean "issue is done with", including "unresolved" if you've made the mistake of adding that to your list of resolutions)

Next, go back into the screens and check you have not put the resolution on any screen other than "resolve issue" - it must never be put on a screen used for create or edit.

Finally, go over your workflows, making sure you only set resolution (via a resolution screen or post-function) when you are moving an issue from an open status to a closed one, and you clear it (not set it to any value) when moving an issue from a closed status to an open one.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events