Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10752

Adding existing Issue to existing Epic should be based on Link permission, not Edit permission

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Answered
    • None
    • None
    • 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.

    Description

      We have several projects in Jira (> 10), with different configurations. Each project has its own dedicated team with its own settings (incluiding permission).
      Usually only some people inside the team have Edit permissions (including Epics).

      Issues in epic are created sometimes by the owner of the Epic, but sometimes also by other people, and ususally in different projects that epic belogns to.
      But there is no way, how user (reporter) of the issue can add its issue to Epic that belongs to other team, even if both users want to link the issues (create Epic link).

      Example:
      User John is owner of epic in project A (John has edit permission in A project)
      User Will is owner of story in project B (Will has edit permission in B project)
      We don't want John to have a generic edit permission in B project and vice versa.

      Usual situation is, that Will finds out that his issue is relevant to John's epic, John agrees with adding the story to epic, but Jira doesn't provide any possibility how to create the epic link.

      Creating of Epic links should be based on Link issue permission rather than Edit permission.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bb5131a6fe29 Jiri Vomacka
            Votes:
            0 Vote for this issue
            Watchers:
            16 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: