Is it possible to capture from Bitbucket things like branch creation date / merge date in JIRA?

[Greg McCarthy]

To expand on the title, I'm endeavouring to create a JIRA dashboard to allow us to see certain metrics around how we release software.

As an example, things like:

- Amount of bugs found in a released version
- Bugs raised during release testing
- How long a release cycle lasts

These are a few examples, but not all. One of the things I'm struggling to capture is how long our release cycle takes. I think if it was possible within JIRA to capture things like when a branch was created (Code cut) and when a PR is merged I might be able to do this more succesfully.

Is this possible? Has anyone else come across similar struggles whilst trying to collate similar metrics? If so what was the solution you reached?

Any and all help would be extremely welcome.

[Earl McCutcheon]

Hello @Greg McCarthy ,

I do not have an exact example in mind but more so going over some theory you should be able to use to get desirable results.   But the first point is that there are no dedicated devtools related gadgets so any dashboard gadget available are going to require a JQL search and referenced field to return as an identifier

Now there are some possible JQL searches for devtools related search terms are covered in:

• Advanced search reference - JQL developer status

Noting you could look into something like pull requests, commits, reviews, and builds to get returned data points, but there is not currently a repository-related search term.

Next thinking on this a bit if have a Jira issue for each bug, and have a date somewhere in Jira that dictates how long a cycle lasts, it should be possible to just compare the dates within the current and previous cycle and then scrape for all bug tickets opened in that window or all bugs with a specific tag associated on them.

I am thinking you could use automation rules to tweak your  workflow to add a label or value to a custom field tag to the tickets as they work them should make locating them with simple JQL pretty easy,  Check out the following thread for some details on automation triggers that can be used for actions done in bitbucket to populate the desired identifiers on the Jira side:

• New automation triggers across Jira Cloud, Bitbucket, GitLab & Github!

Once you are able to define the criteria for adding the desired details to the issues fields for a unique query point with the automation rules, you can then create filters to pull out related issues for those identifiers like created >= "date" AND customField_EXE in (x,y,z)

I also recommend checking out the Advanced Search documentation before defining what custom fields are needed so that you have a good idea of what search terms are possible for various field types.

hope this helps get you on the right track.

Regards,
Earl