Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to make the Resolution field editable? Edited

In our Jira software, we are using the Simplified Workflow, which consists of statuses To Do, In Progress, In QA Testing, and Done.

 

While viewing any bug, we see the resolution field but it seems to not editable:

Resolution field.png1) Do I have to make changes in the workflow?

2) Why is that field coming up in the first place if I don't have it in my workflow?

3 answers

You do NOT make it editable.  You should only set it when closing an issue, and, you should *always* set it, or Jira does not work properly.  It does not matter if you think you don't use it, Jira needs it to be used properly.

See yesterday's discussion on the same matter at https://community.atlassian.com/t5/Questions/Can-not-Edit-Resolution-Field/qaq-p/749848

If you do not want to ask the users to select one, then instead of a screen, use a post-function for "set Resolution to ..." on the transitions instead

I want to make the resolution field visible (or clickable) to users so they can use other resolution fields such as Unresolved, Can't reproduce etc. How can I do that? These fields are not in the workflow.

Again, you do NOT do this.  If you make it editable, your users will corrupt your data.

Please read the conversation linked to, I don't want to repeat it again.

Hi @Nic Brough _Adaptavist_ 

I totally agree with you, the resolution field should never be editable!!  However, someone, somehow in my organisation has made it editable in one of the schemes.  As I don't know how you would make it editable in the first place I don't know how to undo it. 

Any ideas?  I understand if you don't want to reply on this thread though, as that would essentially be providing instructions on how to make it editable in the first place...

Thanks, Liz

Look at your list of screens and where they are used.  Any screen that is used for "create" or "edit" issue in the issue type screen scheme needs to be checked for the resolution field - remove it from any screen that is for create or edit because they are wrong.

Like Liz O'Connor likes this

Found and fixed!!  Thanks for your help @Nic Brough _Adaptavist_ 

Glad it was helpful!  The way resolution works is one of the weirdest hangovers I've seen in Jira, and it's rare to find any admin who has not got it wrong (or seen one of these conversations before they get it wrong).   Takes me back to when I got it so so wrong (I'm old - I'm talking Jira 2 at this point!)

Nic,

Great making the Resolution field isn't recommended by Atlassian.

My business process requires this ability, so how do we enable it without requiring a new screen or a transition.

It's not "not recommended", it breaks things.

Your business process needs to be adapted in a way that allows you to set up Jira to support it.  Have a look at the linked conversation.

If the issue was closed in error, then re-opened, the resolution also doesn't change to To Do. Is there a fix for that?

Your workflow is not clearing the resolution on the re-open transition (you shouldn't have a resolution of "to do" by the way, resolution being empty is what indicates that the issue needs something doiig)

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

79 views 1 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you