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

Resolution is not showing as resolved

vivuu
Contributor
December 6, 2017

After making a issue status to "Done" the reslution should be resolved. but now its not making any change.

 

At the moment marking stories as done, does not mark them as resolved.

 

We need to be able to have this set correctly as it drives behavior in the sprints (actually puts a strike through the key and stops it being edited after it is done).

3 answers

1 vote
Tiffanie P
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 17, 2020 edited

If you have a post function that adds Resolution = Done to the Done transition, then you need a post function that removes the resolution when moving back to "incomplete" statuses. Something like this... 

resolution.png

Ha Tran March 16, 2021

How to set this post function?

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 17, 2021

You  go to where Tiffanie is showing (admin -> workflow -> edit workflow -> find the transition, you'll see the four headers in the screenshot), and click "add"

0 votes
vivuu
Contributor
December 8, 2017

attachment is the current workflow.

Requirement.


Here when we create a new issue in story issuetype for this project , the status will be in "To Do: and Resoulution will be in "Un resolved"

1) We need this resolution "un resolved" for all the cycle of workflow till "Ready for Demo" Status.

When we move the status from "Ready for Demo" to staus "Done" , we need the resolution set to resolved(or Done), and would need a cross line across the issuekey as visible in sprint .( We tried with a post function and resolution is getting updated as ""done". But strike line is not appearing on issue key)

Also from Status "To Do " To "Done" ned the same setup as explained above. (resolution should be changed from unresolved to resolved and a strike over the issuekey as shwing resolved in sprints)

When we are moving the status from "Done" to "TO DO", still the resolution is showing as "Done" , but its not going as "workflow.jpg un resolved."

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 8, 2017

Ok, two things here

>We tried with a post function and resolution is getting updated as ""done". But strike line is not appearing on issue key

Correct.  The strikethrough is only shown in places where it is not clear that the issue might be resolved.  When an issue is in your "done" column, you should be able to assume it is resolved as well (and you have set up your workflow to do that correctly in most places)

>resolution should be changed from unresolved to resolved

Yes, you are missing the "set resolution" post function on the transition from To-do to Done.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 6, 2017

What have you set up in the workflow to set (and clear) the resolution field?

vivuu
Contributor
December 6, 2017

HI Nic,

 

I hope the below is the reson.

 

We have used the default work flow before and it had a post function as below.

 

Type: class
Class: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction 
Arguments:
field.name = resolution
field.value = 10000

 

So the issue moved to done at that time is showing the resolution as "Done" when it moved to Done.

 

 

But 3 months before we created a new work flow for the story issuetype and to done status we havent added any post function. So the issues are showing as unresolved even after moving to done status.

 

So here what action we can do ? to make the resolution to  :resolved " once the status is updated to Done.

 

Also what action can be performed to all the existing issues. 

 

 

What is this post function means , the old one,

 

Type: class
Class: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction 
Arguments:
field.name = resolution
field.value = 10000

can we use the same post function here now ? or not means how to enable ?

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 6, 2017

Seems simple - your old workflow correctly sets a resolution in a post-function.  The new workflow does not, so issues remain unresolved.

You need to add a post-function or screen with the resolution field to all transitions that go from <open> to <we see this as closed> status.

vivuu
Contributor
December 7, 2017

So i have added a post function for resolution - DOne from To do Done. it reflecting.

 

But the problem is that  its not showing the cross line across the issue key whose status and resolution is "Done".

Also after moving the issues from TO Do to Done, its resolution is getting "Done". But again moving to  "To Do " still resolution is "Done"

 

We need to be able to have this set correctly as it drives behaviour in the sprints (actually puts a strike through the key and stops it being edited after it is done).

vivuu
Contributor
December 7, 2017

Any suggestion Please

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 8, 2017

I am not clear on what you are doing here.

Could you explain what you are seeing on the issue view for an issue - what does the resolution field look like before your transition and after?

Then can you tell us where you expect to see the strikethrough?

Finally, have you put "do not allow edit" flags on the *status* in the workflow (resolution does not do anything to stop edits)

Like • Varun likes this

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, ace, atlassian community event, donation, girls who code, women in tech, malala fund, plan international, kudos, community badge, badge, atlassian badge, International Women’s month, International Women’s Day, women's month, women's day

10 for Change at Atlassian Community Events

Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!

Join an Atlassian Community Event!
AUG Leaders

Upcoming Jira Events