microsoft / azure-pipelines-jira

Azure Pipelines for Jira

Azure Pipelines for Jira

Add release information from Azure Pipelines to Jira issues

Giving teams a choice of tools for configuring development pipelines helps establish a successful DevOps ecosystem and enhances collaboration between cross-functional teams. High performing teams operate at their best when best of breed systems work together to give a powerful development pipeline that enables users to retain context as they move between systems for details.

Jira Software is an established and market leading issue tracking system, for agile teams to plan, track, and discuss work amongst them. Using Azure Pipelines, teams configure CI/CD pipelines for applications of any language, deploying to any platform or any cloud.

Azure DevOps and Atlassian have partnered together for Azure Pipelines integration with Jira software. Get started with the integration as described here. Contact Us for more details.

Azure Pipelines integration with Jira connects the two services, providing full tracking of how and when the value envisioned with an issue is delivered. Using the integration, teams can setup a tight development cycle from issue creation through release. Key development milestones for an issue can be tracked from Jira.

Associated Jira issues can also be viewed in builds and releases for a complete deployment history per environment.

It is common for teams to use Jira for issue tracking, GitHub or Azure Repos as a source repository and Azure Pipelines for CI/CD. Developers use smart commit syntax to link their commits to Jira issues, while Azure Pipelines automatically keeps track of the commits consumed in each build and release.

By adding build and release information from Azure Pipelines to associated issues, we complete a three-way linking of information. Teams can start from any of the three services to get planning, development and deployment details for a capability. Jira users can understand whether the feature can be used by end customers, developers can track whether their commits have been deployed to production, and release managers can create release notes in a jiffy.

Get started by installing Azure Pipelines integration with Jira to connect your Azure DevOps organizations with your Jira cloud instance. You can connect multiple organizations with one Jira instance and get data for all your teams and related projects. Learn more

Contact us for more details.

For more information on supported scenarios, refer to FAQs.

azure-pipelines-jira's Issues

Was support dropped?

Listing is pulled from marketplace for both public / private listings, almost all the comments are from 2020, and I can't find a straight answer.

One JIRA project fails to receive deployment info

I have set up the necessary connections between JIRA and Azure Pipelines. I have 5 different JIRA projects, and everything is working in 4 of them.
How can I troubleshoot what is wrong with the last project?

Should this extension work for Jira + BitBucket + Azure pipelines?

The documentation tutorial shows an example of Jira + GitHub + Azure Pipelines integration; as a prerequisite, it states that "GitHub for Jira" should be installed.

We are using BitBucket and are using Jira issue keys in commit messages;
our JIRA issues do show Development integration for Pull Requests etc:

I did follow the tuturial to install and configure the extension;
However,

• in JIRA, no "RELEASES" section is added to the issues
• in Azure Devops, the "Work Items" are not appearing in the release pipeline

Is this related to using BitBucket instead of GitHub?
I would expect this to work, since the JIRA tickets keep track of the BitBucket commits.

Thanks for your time,
Koen

Update on JIRA integration for multi stage YAML pipelines

As per microsoft/azure-pipelines-yaml#455

Is there any mention of when we can expect JIRA traceability for pipelines besides just release pipelines (which have been heavily favoured to be phased out in favour of multi stage YAML pipelines)?

Support for Azure DevOps Server? (on-prem hosted)

Does this integration support Azure DevOps Server? (on-prem hosted)

Based on all documentation it looks like this integration is specific to Azure hosted managed Azure Pipelines. It would be really great if you could use it with Azure DevOps Server's Pipelines as well which is an on premise hosted version of the same service.

Maybe this is already supported but just not documented?

Will this integration be available for Jira Cloud and/or Server?

Functionality-wise this seems like just what we need, and we are eagerly waiting for its release.

Looking at the similar integration for Github, it only support Jira Cloud. So what would be supported for the azure pipelines integration? Obviously we are hoping for Jira Server as well.

Thanks!

Can't see the "Releases" field in Jira tasks

Hi,
I'm getting the same error reported in #15 .
I looked at the available issue fields in the configuration and it isn't there.

I also took the time to uninstall/reinstall the jira app and Azure DevOps service connection.
Can you please help me out?
Thanks.

Jira Keys are Case Sensitive

Describe the bug
When committing, the Jira issue key must be the same Capitalization. I don't know if Jira keys are case sensitive (this issue is assuming that they aren't), but it would be nice if when looking through commits it could case-insensitive.

In Jira, if you try to navigate to issue key abc123 it will redirect you to ABC123 so I assume it is not case sensitive.

To Reproduce

1. Create a commit with a Jira key such as abc123 in the commit message.
2. Release it in a pipeline.
3. Observe it does not appear in the Work Items section of the AzureDevops pipeline.

Expected behavior
Either an option to make it case insensitive, or at least a mention in the documentation that it is indeed case sensitive.

Screenshots
There is a commit "brmi-361" that does not pick up the Jira issue.

Desktop (please complete the following information):

• Browser Chrome
• Version AzureDevops Git Repo + AzureDevops Pipeline + Jira

Support for Multi-stage pipelines

Hi Support Team,

Does the plugin supports Multi-stage pipelines? Was not able to find any documentation on that.

Thanks!

BitBucket integration

Will you support BitBucket in the future or is this a GitHub only project?

Support for TFVC Source Control in Azure DevOps

Is there support for AzureDevOps TFVC for this add in or is it only for Git. In Azure DevOPS in the Release Pipeline Work Item does show the JIRA task. But in the JIRA task there is no Release information like I get when using Git.

Unable to Configure Organization

Describe the bug
We are unable to configure our Azure DevOps organization because it doesn't appear in the dropdown menu. I thought it was possibly a permissions problem, and so I had the DevOps org owner also try configuring it, but he also did not have the option to add the org.

To Reproduce
Steps to reproduce the behavior:

1. Install Azure Pipelines for Jira in Jira Cloud
2. Click on 'Add Organization'
3. See organization does not appear in the drop down

Expected behavior
Populate the dropdown with the correct organizations or provide instructions on how to troubleshoot why an organization may not be showing up.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10
• Browser Chrome
• Version 75.0.3770.100

unable to configure specific project frpm our Azure DevOps organization

Describe the bug
We are unable to configure specific project in our Azure DevOps organization because I am not able to select it from the drop-down menu. All existing Project do show up in dropdown, but I am not able to select it to be able to connect to/with jira.

To Reproduce
Steps to reproduce the behavior:

1. Install Azure Pipelines for Jira in Jira Cloud
2. Click on 'Add Organization'
3. Select organization
4. Try selecting project from dropdown but it’s not being accepted. (See below screen shot)

Expected behavior
Populate selected project from dropdown.

Not Available on Atlassian Marketplace

The link on the wiki no longer works and this doesn't appear to be available in the Atlassian marketplace anymore. Is this a temporary problem or is this gone for good?

Dead

No commits or anything in over 12 months.
I think this integration is dead and should not be used by anyone.

• Doesn't support YAML pipelines
• Doesn't support Jira server

Zero use to our team.

Development / Releases / Deployment tab not showing

I was able to add the Azure Pipelines for JIRA app to our instance and added the JIRA integrations in our release pipelines. However, I do not see any of the integration features in the related tickets, even with the JIRA ticket number in the commit comments and branch names.

We are using git inside Azure DevOps, but care more about the release aspect at this point.

Releases should roll up to related stories and epics.

Currently, release information in JIRA only shows up for the specific ticket that was mentioned in the branch name and pull request. The parent story or epic should also display all related releases.

Get started results in "App is not responding" message being displayed indefinitely

Describe the bug
Once installed, clicking the Get started button results in the message
"App is not responding. Wait or cancel?"
being displayed indefinitely.

To Reproduce

• Install app
• Wait for install to complete
• Click get started
• Observe message

Expected behavior
Some configuration screen should load.

Screenshots
If applicable, add screenshots to help explain your problem.

Uninstalling and reinstalling resulted in the same behaviour.

User account installing the application is both a JIRA admin and Azure Devops org admin.

Abandoned?

So looks like this doesn't work and isn't supported.
Sad.

How do I use this plugin once it is configured and installed?

I just installed the plugin and added a project from within JIRA. I also configured the settings to point to one of my projects in Azure.
Seeing as there no documentation, I am assuming I can attach it from "Add Workitems" option in pull request.
Unfortunately when making a pull request and attempting to add a JIRA workitem, I do not find JIRA as a possible option.

How do I use this plugin?

What is the type of permission need at the Azure DevOps side.

In the documentation it is mentions that the user has to a JIRA admin. But can you please let us know what is the minimum permission required in AzureDevOps

How does Azure DevOps build integrate with task in JIRA

In the documentation you show how Jira integrates with Release. But not sure how Jira will integrate with build. If I have a task in JIRA. When I checkin Is it possible to select work item as the JIRA ticket? I did try putting in the JIRA ID "xyz-1" in the comment section but after that do not see it part of work item after build. I do see the work time in the release section. Could please help what type of integration we can see in the build?
Also we are using Azure DevOps Repo

Support for on-premises Jira Server

Will on-prem Jira Server eventually be supported?

This comment seems to indicate that it will:
https://devblogs.microsoft.com/devops/azure-pipelines-integration-with-jira-software/#comments-501

Whereas this issue comment seems to indicate it is not:
#2 (comment)

Can this issue be used to track support status?

Integration with Yaml Pipelines

It would be great to have this sintegration work with yaml pipelines also, unless I missed something in the configuration. Thanks!

Jira issues not showing on Work items page of Azure DevOps releases

I've followed the instructions at:
https://github.com/microsoft/azure-pipelines-jira/blob/master/tutorial.md
and
https://support.atlassian.com/jira-cloud-administration/docs/set-up-your-deployment-integration/

To install and configure both Git Integration for Jira (to Azure Repos) and Azure pipelines for Jira.
But have only been able to get it partially working.

Jira issues are not showing on the Work items tab on release pipeline in Azure DevOps
and
Deployment information is now showing in the Deployments section of Jira

What is working:

In Jira
I can see and get to my Azure Repos repository from the Code page in Jira
From an issue (user story) I can see the commits that referenceed the Jira ticket key (Id) from the issue (so linking is working properly)
From the Deployments tab it says "You're almost ready to view deployments in Jira"
Development tools connected green tick
Link issues with your development work green tick

In Azure DevOps
Nothing, there are not navigatable links to tickets in Jira

Can anyone help? -- seems so close to getting it working -- have I missed something?

Stage -> Deployment type mapping(s) incorrect after save

Describe the bug

When mapping the (classic) Azure pipeline Stage to JIRA Deployment type it appears to save successfully, but after page refresh - it shows the incorrect values..

To Reproduce

I have 3 Stages in my pipeline, Integration, Staging and Production - when mapping these as follows and clicking save, observe the desired output:

The response from vsrm.dev.azure.com comes back with a json response that causes the interface to show the following (only visible after a full page refresh)

It appears that all desired values I entered have had their index shifted by -1 relative to their Stage.

Looking at Fidder, the properties and values for the Stage-> Deployment type mapping appear to be saved as child properties of the correct 'Stage', but the response is incorrect:

Expected behavior
To save the properties of the Stage with correct values

Screenshots
See above inline

Desktop (please complete the following information):

• OS: Windows
• Browser Chrome
• Version 75.0.3770.100 (Official Build) (64-bit)

Unable to connect Azure

When clicking continue to create the connection to Azure Devops it comes up with Oops and looking in Dev Tools a Internal Server Error occurs (500).
It does seem to create the connection as I can see the details under OAuth Connections.

However through the pipeline options

Any Ideas?

How to search within Jira?

Hi,

How do I use JQL to search for issues with a particular release status. My goal is to automate the transition between Jira issue statuses.

Thanks

Cannot Install Azure Pipelines for Jira in the Jira and use it

Describe the bug
Cannot use the plugin Azure Pipelines for Jira and install it.

To Reproduce
Steps to reproduce the behavior:

1. Log in Jira.
2. Apps->Manage your apps->select Azure Pipelines for Jira->click the button Get started->get the 500 error
3. Apps->Find new apps->select Azure Pipelines for Jira->click the button get free->then get the error: We ran into a little trouble
4. See the screenshot

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Using Azure Devops git repository

I have tried to get this up running within our organization, but it is not clear for me if this integration only supports GitHub and not Azure Devops GIT.

1. The organization is setup in the Azure Pipelines app manager in Jira - no problem
2. I mapped the stages in my release pipeline - no problem
3. Commits with ticket reference to jira - no problem
4. Running a release pipeline does not update the tickets in Jira with release information.

Do we need to install another 3'party app in Jira to get GIT connectivity or is this an error ?

As a side question... will it only update the tickets when all stages has been completed ?

Create a Jira Id status policy

We've been using this for months now and it works great 99% of the time. The 1% that isn't great is when a developer forgets to put the id in the comment or the pr title.

The way we want to solve this problem is by creating a custom status policy that examines the source branch (feature/TST-123) and checks if that appears in the pr title or description or comments of any of the commits. This seems like such a common problem that I wanted to suggest adding it to the project so that everyone can get it instead of everyone having to implement it and in slightly different ways.

Obviously, the branch has to fit the pattern and be found in Jira before it becomes active. From there an admin will only add it as a required policy where it makes sense. For us, this would only be on PRs targeting the master branch.

Update documentation

Describe the bug
There are references in the documentation to features that don't exist. Please update the README and tutorial files to not mention things that do not exist. Also, the supported/unsupported list at the end of the tutorial.md should be moved to the readme.md

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://github.com/microsoft/azure-pipelines-jira/blob/master/README.md'

2. This statement is FALSE: "Azure Pipelines integration with Jira connects the two services, providing full tracking of how and when the value envisioned with an issue is delivered. Using the integration, teams can setup a tight development cycle from issue creation through release. Key development milestones for an issue can be tracked from Jira."

3. Image below it says "Track entire development cycle..." This is FALSE. Only works on v1 pipelines which are classified as "releases" .

4. " Associated Jira issues can also be viewed in builds and releases for a complete deployment history per environment." FALSE - remove "builds", reword "complete deployment" (testing environments may be done in prior stages to "release")

5. Add link to tutorial.md in the README , so people can find it easier when trying to decide not to use this tool.

6. Go to 'https://github.com/microsoft/azure-pipelines-jira/blob/master/tutorial.md'

7. "FAQs" section should be moved to the README.md

Desktop (please complete the following information):

• OS: ALL
• Browser ALL
• Version ALL

Smartphone (please complete the following information):

• Device: ALL
• OS: ALL
• Browser ALL
• Version ALL

Unable to connect Azure DevOps > Jira

Describe the bug
We're unable to connect our Azure Devops to our Jira Cloud account.

To Reproduce
Steps to reproduce the behavior:

1. Install plugin on Jira Cloud
2. Add organization
3. Azure DevOps -- Select your Azure DevOps organization
4. Azure DevOps -- Select a project
5. Click continue
6. Error Message: "The requested resource does not support http method 'GET'."
7. Try again previous steps
8. Error Message: "Service connection with name ****** already exists. Only a user having Administrator/User role permissions on service connection ****** can see it."
9. The Azure account now shows up on the plugin in Jira, but we still can't get it on the DevOps

Expected behavior
Able to select our Jira Cloud account on the Azure DevOps pipelines

Screenshots

Desktop (please complete the following information):

• OS: MacOS & Win 10
• Browser Chrome

Feature request: add possibility to define your own deployment types in the mapping towards stages

It would be nice if we could define our own deployment types in the mapping towards the release stages for the integration. By doing this we could label the deployments according to our own terminology used for different environments.

unable to add organization

Plugin installed successfully but when i click on "Get Started", its throw 404. Please advise if this plugin is in development?

Development section in layout no longer appearing in JIRA

This once worked, but now any JIRA tickets linked to a release do not have any pipeline release information showing up in JIRA. The entire "Development" section is missing, even though both the issue and bug layouts contain the "Development" section as visible.

I am using Azure DevOps for Repositories as well. This used to work just fine.

Getting started is always stuck - App is not responding. Wait or cancel?

doesn't look like this issue is resolved yet. I am facing the same issue today. After multiple install / un install / reinstall cycles, I am still getting the same message even after waiting for more than 30 mins... please help me resolve this issue.

• I have jira cloud instance
• I installed the plugin and hit Getting Started
• no progress after that and keep seeing the following page:

Not working anymore...

...Azure Pipeline for Jira is not available any more on Atlassian Marketplace
...if installed before it was removed, it can not be configured anymore, organization cannot be added anymore
...if configured before removal, deployments are not added to jira, no event is triggered by Azure DevOps release pipeline
...also organization cannot be removed from configuration

As there are so many users relating on this app, please fix all that issues. There is no alternative for that. Service Hooks are not able to send a proper data payload to Jira Automation Web Hook Url. And all other Automation Tools do not support Azure Release trigger.

When will be available this integration?

Hi!

This integration will be very useful for us! When is it expected to arrive? any ETA?

Thanks for this work!

Unable to edit/remove/re-add existing AZ organisation in Jira

We've had a succesfully working Azure Pipelines <> Jira connection for a about a year. Recently it just stopped working, failing to provide any environmental release information towards Jira.

I have tried to remove our connection via the /plugins/servlet/ac/com.azure.devops.integration.jira/azure-pipelines-post-install-page page, but on removal, it shows this error message:

Invalid request: The payload does not match the hash provided.

Also, when trying to add the same organization again, it throws an error as well. Sometimes this one:

The signature is not valid.

Or an error like this:

It seems our AZ Pipelines <> Jira connection is in some kind of a corrupted state and unable to mutate in any way.

Is there a fix/workaround to resolve this issue? Perform a magic reset somewhere? Any help would be appreciated :)

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Make project Open Source

Can you make this project Open Source? I would like to enhance this integration for our team and propose as pull requests. We use TFVC and Pipelines in DevOps, and only Jira for project/task tracking. I don't want to pay 3rd parties for different integrations. I would like to build it in to this integration.

Thanks,
Eric

Validate user story status before accepting the pull request?

Team,

We have a use case in which we need to accept PR merge to master only if user story is accepted.

Do we have this feature in azure devops and jira integration. We have done the same in Rally and github integration. Anything available in jira and azure devops.

Thank you

Feature request: Update status on JIRA issues

We are using JIRA cloud for issue handling. Our source code is in Azure Devops Repos, and we use Azure Devops Pipelines for build and release.

It would be nice to set it up, so that a JIRA issue is automatically transitioned into another status, when Azure Pipelines has completed a deployement to a specific environment?
The issue number is references in the Pull Request title.

Release data not presenting in Jira after pipeline deployment

After setting up the "Azure Pipelines for Jira" app a number of months ago, the sync of release data on pipeline deployments has stopped working. All development data is still synced (Azure Repos via a different app) however no release data now presents on Jira issues. Is there any additional info (settings/logs) that we can use to help identify the cause of the issue?