Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-75833

Related Issue # should display (only) even when a user doesn't have access to that related project

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Obsolete
    • Issue - View
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Requirement: Related Issue Number should display even when a user doesn't have access to that related project but can be disabled since the user will be unable to access it.

      Use Case:

      User "John" has access to projects SAMPLE and PRODUCTION.
      User "Elizabeth" has access only to project SAMPLE.

      The project SAMPLE has a ticket SAMPLE-1001 related to a ticket PRODUCTION-9876.

      When on the ticket description page of SAMPLE-1001, "John" is able to see the Linked Issue where as for "Elizabeth" the linked issue is not at all displaying. This masking here misses to represent the link.

       

      Suggestion: Linked issue PRODUCTION-9876 to be displayed for "Elizabeth" while viewing the ticket SAMPLE-1001, but the hyperlink can be disabled. This will facilitate the user to understand there is a parent / related ticket to this issue and can contact the respective team for additional clarity on need basis.

       

      Thanks.

      Reference URL: https://community.atlassian.com/t5/Jira-Software-questions/Related-Issue-should-display-only-even-when-a-user-doesn-t-have/qaq-p/1574273?utm_campaign=mentions_answer&utm_content=post&utm_medium=email&utm_source=atlcomm**

      Attachments

        Activity

          People

            Unassigned Unassigned
            c29836d6-b056-41e6-97a0-a5dfcf20e8aa Deleted Account (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: