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

Cannot restrict an issue linking using a permission scheme

XMLWordPrintable

      Steps to reproduce are below:

      1. Create two projects (PA and PB)
      2. Configure the permission configurations, so that current the user have the permission to create links in PA project, but does not have this permission in PB project.
      3. Create two issues (PA-1 and PB-1)
      4. Try to create any link from PA-1 (linking should be allowed) to PB-1 (linking should be not allowed).

      Other steps:

      1. Move one of issues in PA project (where I can create links)
      2. Create a link from moved issue to the another one.
      3. Move that issue back in PB project.

      Currently, JIRA system allows users to create an issue link. It would be great if JIRA is able to display an error message and validate the link, where it should not be created since the current user does not have permission to create link in PB issue.

            [JRASERVER-31248] Cannot restrict an issue linking using a permission scheme

            Alicia Pena added a comment -

            We really need this feature implemented.  We need to freeze maintenance windows and disallow further linking to particular jira's.  Neither the status or transition jira.permission.link.denied works to stop other projects from linking.  The permission scheme doesn't block links either.  What's the point of stopping a project from outgoing links?  It makes more sense to prevent incoming links to the project.

            Alicia Pena added a comment - We really need this feature implemented.  We need to freeze maintenance windows and disallow further linking to particular jira's.  Neither the status or transition jira.permission.link.denied works to stop other projects from linking.  The permission scheme doesn't block links either.  What's the point of stopping a project from outgoing links?  It makes more sense to prevent incoming links to the project.

            Soner Kalaycı added a comment -

            We really need this to be implemented! Linking should honor both side's permissions either in creation or deletion.

            Soner Kalaycı added a comment - We really need this to be implemented! Linking should honor both side's permissions either in creation or deletion.

            Eric Dalgliesh added a comment -

            I don't think the target link has ever been restricted, but ideally it should be.

            Eric Dalgliesh added a comment - I don't think the target link has ever been restricted, but ideally it should be.

            MattS added a comment - - edited

            I always read Link Permission as "can the user create a link on a (source) issue in this project". I don't think the target issue was ever restricted, was it? I suppose the docs could be clearer about this

            MattS added a comment - - edited I always read Link Permission as "can the user create a link on a (source) issue in this project". I don't think the target issue was ever restricted, was it? I suppose the docs could be clearer about this

              Unassigned Unassigned
              ckimloong John Chin
              Affected customers:
              12 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated: