In a pull request, you can view the JIRA issues associated with a pull request. I know that typically, a pull request should be lite on the number of issues it is fixing, but we've found in our Gitflow process that pull requests are a useful way of viewing exactly what is getting merged into a master branch from a release branch. Since a release to master merge can include lots of changes, is there a way to up the limit on the number of JIRA issues you can see in pull request?
Community moderators have prevented the ability to post new answers.
Looks like ticket STASH-7779 was marked resolved with no fix
Here's another way to get the list outside of BitBucket
prev_release=vN.N.N; git log --oneline $prev_release...origin/develop | grep -Eoh "<prefix>-[0-9]{1,5}" | sort | uniq
Hi Christopher,
I've put in a feature request on this which can be found here: https://jira.atlassian.com/browse/STASH-7779.
Please be sure to watch it, and vote on it, so that you're notified if this feature request will be implemented in a future release.
For your reference, you can find our policy on how we prioritise feature and improvement requests: https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy
Cheers,
Andrew Er
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.