Improve Jira Integration Terminology and Behavior in Merge Requests

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Proposal

Improve GitLab-Jira integration terminology and behavior in merge requests to provide more accurate and user-friendly experience.

Currently, the GitLab-Jira integration presents several usability challenges:

1. Displays misleading "Closes issues" terminology even when Jira transitions are disabled
2. Automatically adds "Closes" prefix to Jira issue IDs regardless of transition settings
3. Removes automatically detected Jira issue IDs when changing merge request templates

Proposed solution includes:

1. Context-Aware Terminology

   • Change "Closes issues" to "Related issues" when Jira transitions are disabled
   • Use terminology that matches actual integration behavior

2. Configurable Issue Reference Prefix

   • Allow admins to configure prefix for automatic issue references
   • Default to "Related:" when transitions are disabled
   • Support options like "Related:", "Resolves:", "Closes:"

3. Preserve Issue References

   • Maintain detected issue references when switching templates
   • Store issue references separately from template content

Benefits:

• Clearer communication about Jira issue status changes
• Reduced user confusion
• Improved workflow efficiency
• More consistent experience between GitLab and Jira issues

Implementation requires changes to:

• Merge request UI
• Automatic issue detection system
• Template selection mechanism

---

Description was generated using AI