Hi Everybody,
We use Jira Cloud and Bitbucket Cloud. I have enable the option Development in Jira, so we can see the created branches and open pull requests.
Is there way to disable the transition to state CLOSE when there are open pull requests?
I like to hear from you!
Thanks a lot!
Michiel
Hi Everyone,
If anyone is looking for a solution still and interested to try out new plugin, we have released a FREE plugin which blocks the transition if there are any open PRs.
please find the plugin here: Open Pull Request Condition for Jira
and we would love to hear your feedback.
Regards,
Leo, CodeForMe
I was able to do it with the ScriptRunner script validator.
The following code should be added:
issue.customfield_10000.match('OPEN') == null
My configurations is Jira Cloud + Bitbucket Data Center.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@David Fischer - Anyway to do this with JMWE? I have the same need.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @John Funk
Unfortunately, Worfklow Conditions and Validators for Jira Cloud can only be written in Atlassian's "Jira Expressions" language, which currently doesn't expose Development data.
However, it would be possible on Jira Server/DC. And it's also possible to access development data from JMWE post-functions on Jira Cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was afraid of that. Thanks for the verification though!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Michiel Jakobs - I think that also probably answers your original question.
What I have done as somewhat of a work around is to have an email sent to me and the Dev lead when an issue with open pull requests is marked Closed/Done so someone can follow up with the Developer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks everybody for the answers. I will implement the work around of @John Funk.
I hope that the development data can be used in Workflow conditions soon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk Hi, can you provide some details on how to setup this email notification when an issue is closed if it still has pull requests not merged yet.
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.