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.
I am trying to use the release warnings. I have 3 issues done, but one of them has an open pull request however, the issue doesn’t appear on the warnings tab.
What am I missing?
Hello Francisco,
Thank you for reaching out to Atlassian Community!
When an issue has an open pull request, it should appear on the Warning tab as mentioned on the documentation:
With that said, I would like to know if you have enabled this type of warning. On the warning tab, click on "Manage warnings" and enable "Open pull requests".
Why can't I see any warnings?
Warnings will only display on the Release page if:
- Jira Software is connected to your Atlassian development tools, e.g. Bitbucket, Bamboo, Fisheye/Crucible; or GitHub. See Integrating with development tools for more information.
- You have the 'View Development Tools' permission. See Permissions overview for more information.
- Warnings are enabled. You can see which warnings are enabled by clicking the Manage warnings button.
Please, give it a try and let us know how it goes.
Regards,
Angélica
Hello Angélica, thank you for the quick answer.
I already enabled the "Open pull requests" option. Here is the screenshot.
But after that, I still can't see any warnings. I notice that if try the following JQL, I can get the issue with status done and an open pull request.
statusCategory = done AND project = DEMO and fixVersion = 1.0.2 and development[pullrequests].open > 0
Regards,
Francisco.
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 details, Francisco.
Testing on my local site, I was able to replicate the same issue.
Based on that, I created a bug for our dev team to check what is causing this behavior:
Please, click on "This affects my team" and also Watch to receive future updates.
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.