This task provides an overview of JIRA integration and progress.
Does Phabricator integrate with JIRA?
===========================
Yes, **but in a very limited way**. These integrations are supported:
- You can add a JIRA 6 instance as an authentication provider.
- This allows users to log in to Phabricator with their JIRA accounts (i.e., you can use JIRA as SSO).
- This also allows users to link their JIRA accounts to their Phabricator accounts.
- If a JIRA 6 instance is enabled as an authentication provider:
- A "JIRA Issues" field will appear in Differential, in the web UI and CLI.
- Users who have linked their JIRA and Phabricator accounts will be able to add issues.
- Users who have linked their JIRA and Phabricator accounts will be able to see issues names in a s
- JIRA issues linked to a Differential revision will be updated (with comments) when the revision is updated.
Here's what the field looks like:
{F168741}
{F168743}
Here are some of the comments on corresponding issues:
{F168739}
What limitations does the integration have?
=====
- No support for JIRA 5 (see T4289).
- No links between Maniphest tickets and JIRA tickets.
- No links between commits and JIRA tickets.
- No support for updating JIRA ticket fields (versus simply commenting on them) when revisions change (see T3837). For example, you can't close tickets.
- No support for importing data from JIRA (see T3179).
- Users must individually link their accounts. There is no support for a single "master" or "bot" account. Individual linking makes sure users can't see anything in JIRA that they aren't normally allowed to see.
What are the plans to improve integration?
=====
This is a //very// low priority for us, and we have no immediate plans to improve integration. All the integration we've built so far has been under contract, and improving these integrations is many years away on our natural roadmap.