Jira integration improvements

This meta issue lists the main enhancements, feature requests and bugs in both EE and CE issue trackers.

Done in 8.13

• Refactor JIRA integration to use jira gem (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2572)
• Bug: Comment triggered incorrectly (https://gitlab.com/gitlab-org/gitlab-ee/issues/828)

---

Future releases

Other important JIRA issues (should be done in a next release)

• Bugs

  • If Jira issue id mentioned in many commits, it is duplicated multiple times in MR (https://gitlab.com/gitlab-org/gitlab-ce/issues/20479)
  • Issues can't be closed after JIRA integration (https://gitlab.com/gitlab-org/gitlab-ce/issues/1981)

• Add remote issue links to JIRA (https://gitlab.com/gitlab-org/gitlab-ce/issues/13232) Need weight

• Ability to configure the JiRA plugin (https://gitlab.com/gitlab-org/gitlab-ce/issues/5541) Need weight

• Better documentation

  • Update JIRA attributes available via API https://gitlab.com/gitlab-org/gitlab-ee/issues/440

• Enhancements (in order of upvotes - the higher in the list, the more votes)

  • See build statuses per commit within JIRA (https://gitlab.com/gitlab-org/gitlab-ce/issues/5994) Awaiting answer
  • Multiple Closes request to Jira issue (https://gitlab.com/gitlab-org/gitlab-ce/issues/20734) Awaiting answer
  • Jira Developement Panel (https://gitlab.com/gitlab-org/gitlab-ce/issues/20418) NOT POSSIBLE AT THIS TIME
  • Two way JIRA integration for comments (https://gitlab.com/gitlab-org/gitlab-ce/issues/20570) Too complex at this time

• Enhancements that looks like bugs

  • Avoid multiple comments in Jira for the same mention (https://gitlab.com/gitlab-org/gitlab-ee/issues/563)
  • Overly verbose comments in JIRA (https://gitlab.com/gitlab-org/gitlab-ce/issues/19825)

cc @JobV

Added meta label

Awesome compliation @regisF. What do you think we should prioritize? What is most requested?

@JobV

Bugs https://gitlab.com/gitlab-org/gitlab-ee/issues/828 and https://gitlab.com/gitlab-org/gitlab-ce/issues/20479 seem to really piss off people (I've seen multiple issues about this).

I've reordered the list of improvements based on the number of upvotes.

The interesting feature in the list is this one: Two way JIRA integration for comments, because if we do have the same comments in both places, that means nothing would be lost if they decide to switch from Jira to Issues entirely.

@regisF alright, make sure bugs are fixed in the next release and see where to fit in the rest :)

Make sure to get an OK from someone that knows about JIRA before scheduling big things though ( @marin was always my expert, but he's super busy).

@regisF @JobV Before starting work on any of the features, I would advise you to consider prioritising full refactor of the Jira service we currently have. Our Jira integration was written with different restrictions in mind and if we want to start adding more we need to take a step back.

My advice is to consider working on refactoring with jira gem which could allow us to have proper oauth and would also allow us to build on top.

Thank you @marin for your input.

What is the amount of work we are talking about for refactoring the current Jira service? @DouweM ?

See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2572.

Lol. At least we are on the same page if nothing else...

@dblessing I'm trying to create a list of things to do for 8.13

Can you give me your advice above and tell me if you think that's right?

@regisF https://gitlab.com/gitlab-org/gitlab-ce/issues/20570 will be really, really difficult. At the moment, if you enable any external issue tracker, the GitLab issue tracker cannot be used. Clicking 'Issues' in the navbar takes you to the external tracker, not GitLab anymore. It's not just an issue of 'two-way comment integration', it's an issue of supporting dual trackers at all. I don't think we should pursue this in the short term.

The other items look mostly reasonable, at a glance. This will definitely require some developer help, though. I am familiar with the JIRA integration and can help but won't have the time to focus on it.

Milestone changed to %8.13

Added ~481018 label

Reassigned to @felipe_artur

We also need to fix a JIRA regression ASAP: https://gitlab.com/gitlab-org/gitlab-ce/issues/22446

@regisF what are / aren't we doing in 8.13 and what should we do for 8.14?

Changed title: Jira integration improvements (Meta) → Jira integration improvements

I've updated the body of this issue to show what we will ship in 8.13, and I've created a new issue listing what we should do in 8.14 here: https://gitlab.com/gitlab-org/gitlab-ee/issues/1134

We'll then be able to close this issue once 8.13 is released.

Added ~874214 and removed ~481018 labels

Milestone changed to %8.14

@regisF can we close this now?

We'll then be able to close this issue once 8.13 is released.

@smcgivern yes we can. I'll close it.

Status changed to closed

mentioned in commit test-nick/gitlab-ce@dcaa2f16