Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Want to remove Resolution field value from NEW status

Sanjivani Wayal
Contributor
August 28, 2023

Hi,

 

i want to remove Resolution field from NEW status of BUG i have done it for other statues and its works fine only when i create a new BUG it still shows as Unresolved . Could you please help me with removing it i have attached the screenshot of Postfunction 

postfunction.PNG

1 answer

1 accepted

2 votes
Answer accepted
Jack Brickey
Community Champion
August 28, 2023

hi @Sanjivani Wayal , are you wanting to ensure the Resolution = Unresolved for Bug issuetype transitioning to NEW or do you wish to remove the field from the screen? Your words seem to convey the latter but the screenshot conveys the former.

Jack Brickey
Community Champion
August 28, 2023

Assuming NEW is the initial status at creation then Resolution should be Unresolved by default. Maybe your workflow allows transition from DONE to NEW?

Sanjivani Wayal
Contributor
August 28, 2023

@Jack Brickey I want to remove Resolution when the BUG is Created (on creation status of bug is NEW)

So as i understand from above is it that when BUG is created Resolution field will be Unresolved only and it cant be changed? 

Jack Brickey
Community Champion
August 28, 2023

By default the Resolution field will always be Unresolved. If it is not, then someone has messed with the Default config or otherwise modified the workflow. Can you elaborate on what you see when creating a Bug? Does the create screen require the user to set the Resolution? is the Resolution something other than Unresolved?

As a matter of clarification - The Resolution field is intended to explain "how" an issue was resolved:

Done >> I addressed the issue or completed the task

Won't Do >> the issue will not be addressed

Duplicate >> closing this issue as a dup of another

etc...

The Resolution field should always (?) be set when moving an issue to it's final status (Done/Closed/etc). This can either be done by the user via a transition screen or automatically in TMP projects or via CMP workflow post function.

The Resolution field should always be cleared if the issue is transitioned out of the final status when 'reopening'. This is automatic in TMP or via Workflow post function in CMP (or Automation if preferred). 

Sanjivani Wayal
Contributor
August 28, 2023

@Jack Brickey  When the Bug is created it is by default showing as Unresolved which as per the customer requirement should not be shown.

 

There are some status where we have done this on Workflow by writing the postfunction and its works fine for eg - if we move the BUG to Assigned from New  status the Resolution field is set as None on workflow and on issue the field value is not shown at all sharing the screenshots for both new and other status Assigned.PNGNew_Status.PNG

Sanjivani Wayal
Contributor
August 29, 2023

@Jack Brickey the main purpose is when the resolution status is unresolved in XRAY report the defect goes to Close status which is wrong

Jack Brickey
Community Champion
August 29, 2023

@Sanjivani Wayal , your customer is right! What I notice here is the green checkmark beside Unresolved when the status is New. This is wrong as "unresolved" should not show there nor have a green checkmark. I believe someone has created a resolution value labeled "Unresolved". Assuming so, this needs to be corrected. Please go to admin > Issues and in the right sidebar look for Resolutions and see if "Unresolved" is listed. If so then there is some work to unwind this as you need to find out who did this and why so that you can implement the correct behavior.

By default Jira represents an empty Resolution as Unresolved. When looking at an issue that is unresolved there should be no resolution and no checkmark.

now the other question is where is the new bug's resolution being set? There are 3 possibilities I can think of here and recommend you check them.

  • post function in the create transition of the workflow (check the transition PF)
  • required field in the create screen (test creating a bug)
  • automation rule (check the history of the issue)
Sanjivani Wayal
Contributor
August 29, 2023

@Jack Brickey  you are super awesome someone had created some automation ages ago and it was creating the problem i missed to check in Automation but thanks to you for guiding me , its solved.

 

Thanks a Ton Jack.

Like Jack Brickey likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events