Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,298,230
Community Members
 
Community Events
165
Community Groups

What are the best practises to collect the release notes when having JIRA - Bitbucket integration?

What are the best practises to collect the release notes IF there are many JIRA projects contributing to the same project/repository?

1 answer

1 vote

Jira's built-in "release notes" feature focuses on a single project.

If you use the Bitbucket integration, then you probably make your commits mentioning precise Jira issue keys in the commits or in the branch name, is that correct? If not, then it is a good practice, because then your commits will be precisely linked to the corresponding user stories, tasks, bugs, etc. This app helps to implement a commit policy  like that.

After that you should be able to collect the issues to be included in the release notes with running JQL queries against the Development field. It works cross-project.

When you have the issues, you can export those to a release notes with multiple apps like this one.

We have issue keys in the commits, isn't that the pre-requisite for seeing the commits in "Development field" in the first place?

You suggestion was looking promising, but there is no way to see the project or branch name in the "Development field", right?

but there is no way to see the project or branch name in the "Development field", right?

If you mean the Jira project by "project", then it is not the "Development" field, but the issue that determines it. If you mean the Bitbucket project, then it may be available.

But the branch is definitely available like this:

development[branches].all > 2

I mean BitBucket project.

The branch _name_ is not available, only the amount of branches.

It seems you're right... I'm surprised, I always thought you can access the related branch names through that field.

But the fact that only the <, =, etc. operators with numerical arguments are supported also suggests that this is a plain number only.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,225 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you