You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Hi,
i created a rule which sets the fix version to the next unreleased version when a issue is transitioned from in progress to resolved. It always works perfect!
Suddenly it does not set the fix version. When I tried to set label, comments too this works. Only the fix version is not set.
Has anyone an idea what's going wrong?
Thanks!
It looks like this would be a bug.
Today several users reported the same:
https://community.atlassian.com/t5/Jira-Software-questions/Next-Unreleased-version-doesn-t-work-for-edit-issue-field/qaq-p/1602593
Can you please check the audit log for this rule.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sandesh Shettythe audit log in my screenshot is from this rule. I only added some manipulation in other fields (label, comment, ...) to test if the "if-else" is not working..
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.
Hi @Stephen Wright _Elabor8_ , sorry - i forgot the screenshots. I added it in my post. Yes I have an unreleased fix version.
Thank you!
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.
I hope Atlassian will fix it when someone opens a bug... https://community.atlassian.com/t5/Jira-Software-questions/Next-Unreleased-version-doesn-t-work-for-edit-issue-field/qaq-p/1602593
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tested this on our instance and found like yourself, the "Next unreleased version" doesn't activate.
I looked through the list of Automation bugs on JAC, and could not locate a bug for this. I would advise raising your own bug via the dashboard.
In the meantime, I did find that it still works if you specify a version - not dynamic, but still possible to use whilst this is investigated :)
Ste
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.
Awesome, I didn't locate this one - nice find :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.