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

    • Icon: Suggestion 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.

      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.

          Form Name

            [JSWSERVER-10752] Adding existing Issue to existing Epic should be based on Link permission, not Edit permission

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3070512 ] New: JAC Suggestion Workflow 3 [ 3663251 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626399 ] New: JAC Suggestion Workflow [ 3070512 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2324079 ] New: Confluence Workflow - Public Facing v4 [ 2626399 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2044890 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2324079 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2033268 ] New: JIRA PM Feature Request Workflow v2 [ 2044890 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 735853 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2033268 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 689748 ] New: JIRA PM Feature Request Workflow v2 [ 735853 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Martin (Inactive) made changes -
            Comment [ A comment with security level 'atlassian-staff' was removed. ]
            Martin (Inactive) made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Jiri Vomacka created issue -

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

                Created:
                Updated:
                Resolved: