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

[Juha Välimäki]

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

[Aron Gombas _Midori_]

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.

[Juha Välimäki]

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?

[Aron Gombas _Midori_]

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

[Juha Välimäki]

I mean BitBucket project.

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

[Aron Gombas _Midori_]

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.