You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all,
I tried to change issue resolution with automation for Jira following advices found in:
https://community.atlassian.com/t5/Next-gen-questions/How-do-you-resolve-or-close-an-issue-in-a-next-gen-project/qaq-p/1050600
However, using the workflow provide by @Sheila Hippert I get an error message, saying that field Resolution may not be on transition screen.
Any idea why this does not work for me ?
Unknown fields set during transition. Field may not be on transition screen. Fields ignored -Resolution (resolution)
Hello Kamal,
Welcome to Atlassian Community!
Thanks for linking the post. I checked her reply and created automation on my local site and it works.
First, I created a new column on my board called "Won't do" and added it before the last column:
Then, I created the automation:
When:
If:
Then:
After that, moving a card to the column, it adds the resolution.
Please, give it a try and let us know how it goes.
Regards,
Angélica
I was using issue fields condition instead of "if block", and for the then part, I was using "Transition issue to".
Anyway I still have some strange behaviour after trying what you suggested. And I don't get why ...
I get for example the following error related to the "if" block:
Thanks for your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I managed to get away from the error I had yesterday, by restarting the rule from scratch instead of editing my previous one. However, I don't see the resolution being updated when moving issues to the "Won't do" column ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kamal,
Thank you for sharing the screenshot.
On next-gen projects, there are three types of status: ToDo (Grey), In Progress (Blue) and Done (Green).
The first column will be ToDo, the last one will be Done that automatically adds a resolution and the other ones between those two will be In progress.
With that said, as per the screenshot, you are using the "Won't do" in the very last column that automatically adds the resolution.
The Green status also adds a resolution automatically by the system, that's why it's not working because the automation and the system are adding the resolution at the same time.
Please, move the "Won't do" to the In progress status and test again.
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually the won't do column is not the last one., as you can see below. The won't do status is in blue.
I tried this:
and this as well:
don't know if that makes a difference but none work.
Just a small notice. In your screenshot it is written "Resolution (system)", while in mine there is no "(system)" after resolution. Seems we are not operating the same version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the information and details, Kamal.
I believe that this "Won't do" belongs to another project and not the project you need. I also faced this issue when created the automation without specifying the project.
Please, go to the Automation rule and click on "Rule details" and select the project:
After that, you will see that only status for that specific project will appear in the dropdown:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't edit the project here on my side, but the one listed seem to be the good one... See picture below...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok... But for some reason, I tested it again and it works...
I don't get it. But I am happy.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Angélica Luz we implemented the rule for all the next gen project. It worked for few days, and now it stopped working.
It seems a bit erratic.
Any idea ?
Best.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kamal,
Have you checked if it shows any information on the logs?
If you let it run for only one project, does it work?
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It worked again on Friday, while I did not change anything. When it was not working, I did not see anything in the logs. It says the rules is ok. When it started to work again, I started to receive the emails when rule applies...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.