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

Resolution in team based project

In team managed projects (business/work management type) it is not possible to select the resolution of the tasks (duplicate, declined etc.) and its ok, but I read that the resolution field should be set to "Done" when the card reaches the rightmost column of the board.

image.png

Within the project, however, the tasks remain unresolved.


image.png

The problem is that this makes it impossible to filter all the unresolved activities of a user who participates in team and company projects, generally it is sufficient to insert a filter with the condition "assignee = currentUser () AND resolution = Unresolved" but that doesn't work

is there any suggestion? I need to se resolution when task is done!

3 answers

1 accepted

3 votes
Answer accepted

Hi @Edoardo Landi 

Looks like it's a bug - confirm it impacts you via JWMCLOUD-180 

Your options for now are...

  • Use a Software Project or...
  • Use a different parameter in JQL - such as Status, or StatusCategory

Ste

thanks @Stephen Wright _Elabor8_ , using status category is a good workaround, even if it is not completely correct (not all states in all projects in the category Done may have to set the resolution, and in this way it is not possible to differentiate the two cases)

Like # people like this
2 votes
Ron Levy Atlassian Team Mar 27, 2022

@Edoardo Landi thx, let us look into this further. FYI @Jane Yeoh 

Hello, it is an annoying bug, so please fix it. Thx 

Like # people like this
Like Atle Andersen likes this

Still outstanding unfortunately

Like Krátki Barna likes this

Managed to fix it with automation: Project settings --> Automation-->Create rule

When: Issues transitioned
FROM (In Progress, To DO, Test, etc.)
TO (Done)

Then: Edit issues fields

Resolution

Done

*Done (if you dont have "Done" resolution type default go to Jira Basic setting/Issue attributes --> Resolution and create a "Done" type with Description, use as default)

Standard reports work with this solution.

On the other hand it also usefull to do an Automation backwards,  when you move a Done ticket back to In progress, Test etc. so the workflow sets resolution back to Unresolved. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events