We have 2 columns on sprint board which are 'In Progress' and 'PR Open'. I have automation setup so that when a PR is opened, the ticket automatically transitions to 'PR Open' status and column.
When a draft PR is open, I want the ticket to remain 'In Progress' but this isn't happening, what am I doing wrong? I thought adding the check on the pull request state would work, but it doesn't. I've tried 'DRAFT' and 'Draft' to identify if it's an issue with the casing but it's not.
I'm trying to work around the lack of functionality which would be fixed by https://jira.atlassian.com/browse/JRACLOUD-72888, which we have been waiting years for
Thanks to the above I have identified a solution which works:
Hmmm seems to have caused another issue...now when the pull request is transitioned from draft to open, the ticket no longer transitions from 'In Progress' to 'PR Open'...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I looked into this, and haven't found an available development variable to check the transition from draft to open (ready to review) state. But your solution is more than half-way there for me!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What if after the trigger, you write to the audit log the value of {{pullRequest.state}} to confirm the value? That may help you identify what needs to be tested in the condition.
I wonder if that is an enumeration, and there is a lower attribute that could be checked.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! I tried that and it looks like the case for 'DRAFT' is actually 'draft' so I've updated my automation rule again and hope this works next time the rule is run.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well done, and thanks for posting that in the open suggestion as well! That will benefit the community...and perhaps Atlassian will update the documentation to match what you found for the additional value in that field :^)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've had to disable it unfortunately...it's had the unintended consequence of preventing any tickets with a true open PR from transitioning to 'PR Open' status when they are no longer in draft and these tickets are now remaining 'In Progress'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wonder...
If you map out the flow to confirm the states and your processing timeline, could you capture when draft occurred in the issue (e.g., in a custom field, label, or entity property), and then either modify this rule (or use and additional one) to handle this case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your suggestion, I'm not really sure what to do and would rather not have to implement such a workaround for functionality which should be available. I think i'll just have to wait X many more years for https://jira.atlassian.com/browse/JRACLOUD-72888,!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kara Nadarajah ,
What if you use the "Does not contain" option instead of the "does not equal" option in the if statement?
Kind regards,
Bert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, I tried but it hasn't worked either. The status has still been updated to PR Open.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.