Customize Environment Names for CI/CD
Jira supports specific environment names. When Environment names do not match or are using different words, the information is missing in the deployments view. Allow Customers to enter specific environment names and map them to Jira's
Pull Request API for DC
Add API services to handle display information for Pull Requests for Jira Data Center.
Add Approvers and ability to Approve directly in Jira
One of the biggest things we were looking at for usage of the plugin was the ability to have BAs/QAs not have to go into BitBucket to approve Pull Requests and be able to add Approvers directly from Jira.
Azure DevOps yaml release pipeline support
Currently, the plugin only supports Classic Release pipelines. While these are great for most use cases, some customers do use the power of yaml pipelines were they can define multiple stages and steps.
Github repositories added as Jira Asset
We would like to be able to show github repositories within Jira and Confluence. If all synched Repos was possible to add as an Asset in own devops object schema this could be reused within actual fields in Jira as well as in confluence pages....this would be soo sweet:)
Enable matching Gitlab user to Jira user with Automation
We would like to use Jira Automation to, upon the creation of a branch in Gitlab, assign the corresponding issue in Jira to the user who created the branch. This means that there needs to be some way to translate the Gitlab user into the Jira user. This is already being done elsewhere: when using the GIJ repository browser in Jira, the most recent commit to the currently viewed branch is listed at the top, along with a username. A Jira username. Meaning, when someone makes a commit in Gitlab, GIJ somehow already manages to match that Gitlab user to the corresponding user in Jira. (I suppose it helps that both Gitlab and Jira use the same AD on our end.) So perhaps GIJ could provide something that the Jira Automation action "assign issue" can understand, such as feeding it the "user that triggered the event", or providing a custom smart value that can be manually referenced there.
Improve display name configuration for Connection to Gitlab
When creating a connection to Gitlab, the "Display name" (otherwise available in the API as optional) is not available in the form, and is automatically set to the gitlab URL. If multiple connections (e.g. to different groups in the same Gitlab instance) are created they all appear with the same display name. Once created, it is possible to edit the display name, but then the target URL is not visible anymore anywhere, not even as a readonly field. Is it possible to add the possibility to set the display name up-front in the « Connection to gitlab » form, and to add a display of the URL in the edition form?
Expand information on current reindex progress
Sometimes the reindex feels like it's up and it's hard to tell if it's still running or hung. I would like to have more information about what is happening now. For example, to show the progress of processing commits.
Jira Insights and CI/CD for Jira DataCenter
Team do you have any plans to offer the Insights or CI/CD for Jira DataCenter
In the Commit View, add an option to disable grouping by repository
we are using now jira cloud with git plugin. On our server jira was no group for each repository, so we don't care to split our project in different parts at Bitbucket. But now we see every part as separate repository and every repository as a group in git commit view. That's why we want to add the possability to "not group" by repository.