Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-29295

Make JIRA.Mention controller accept optional REST URL to enable re-use

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      I noticed that JIRA.Mention is now using Backbone.js and the old implementation is available as JIRA.LegacyMention

      That is great but I had extended the old implementation to provide alternative REST endpoint (/user/search instead of /user/viewissue/search). This breaks in JIRA 5.1.2

      It would be ideal that the JIRA.Mention would just accept options to either use custom endpoint and/or simply use /user/search when projectKey is not provided. That way I could use JIRA.Mention without hacking to get it to work with non-project specific mentioning.

      Thanks.

            [JRASERVER-29295] Make JIRA.Mention controller accept optional REST URL to enable re-use

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

              cdarroch Daz
              18a323a8360a Viðar Svansson [Tempo]
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: