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

Sprint in openSprints() throws error because no Browse Project permission

XMLWordPrintable

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      No issues are assigned to a sprint with id 120
No issues are assigned to a sprint with id 132
No issues are assigned to a sprint with id 2

      An error will be thrown as above if user is trying to search using openSprints() query even if the user has specified the particular project that he/she has permission to browse.

      Steps to reproduce

      1. Create a project A
      2. Create Scrum 1 for Project A
      3. Create two users where has the following
        • User 1 has permission to Project A
        • User 2 has no permission to Project A
      4. Create issues in Scrum 1 and include them in Sprint 1
      5. Login as User 1 and search for Sprint in openSprints() in Issue Navigator and you will be able to see the issues
      6. Login as User 2 and search for Sprint in openSprints() in Issue Navigator and you will be able to see the following error 
        No issues are assigned to a sprint with id 1

      Expected behaviour

      The error should not be there and should just show that there is no issues found on the query.

      Extra info

      The bug is only in GreenHopper 6.1.3.1. Tested in GreenHopper 6.0.8 and 6.1.2, the error does not persist.

            [JSWSERVER-7661] Sprint in openSprints() throws error because no Browse Project permission

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.01
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2853298 ] New: JAC Bug Workflow v3 [ 2937314 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545772 ] New: JAC Bug Workflow v2 [ 2853298 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550692 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545772 ]
            jonah (Inactive) made changes -
            Description Original: {noformat}No issues are assigned to a sprint with id 120
            No issues are assigned to a sprint with id 132
            No issues are assigned to a sprint with id 2{noformat}

            An error will be thrown as above if user is trying to search using {{openSprints()}} query even if the user has specified the particular project that he/she has permission to browse.

            h3. Steps to reproduce
            # Create a project A
            # Create Scrum 1 for Project A
            # Create two users where has the following
            #- User 1 has permission to Project A
            #- User 2 has no permission to Project A
            # Create issues in Scrum 1 and include them in Sprint 1
            # Login as User 1 and search for {{Sprint in openSprints()}} in Issue Navigator and you will be able to see the issues
            # Login as User 2 and search for {{Sprint in openSprints()}} in Issue Navigator and you will be able to see the following error
            {noformat}No issues are assigned to a sprint with id 1{noformat}

            h3. Expected behaviour
            The error should not be there and should just show that there is no issues found on the query.

            h3. Extra info
            The bug is only in GreenHopper 6.1.3.1. Tested in GreenHopper 6.0.8 and 6.1.2, the error does not persist.
            		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-7661].
              {panel}

            {noformat}No issues are assigned to a sprint with id 120
            No issues are assigned to a sprint with id 132
            No issues are assigned to a sprint with id 2{noformat}

            An error will be thrown as above if user is trying to search using {{openSprints()}} query even if the user has specified the particular project that he/she has permission to browse.

            h3. Steps to reproduce
            # Create a project A
            # Create Scrum 1 for Project A
            # Create two users where has the following
            #- User 1 has permission to Project A
            #- User 2 has no permission to Project A
            # Create issues in Scrum 1 and include them in Sprint 1
            # Login as User 1 and search for {{Sprint in openSprints()}} in Issue Navigator and you will be able to see the issues
            # Login as User 2 and search for {{Sprint in openSprints()}} in Issue Navigator and you will be able to see the following error
            {noformat}No issues are assigned to a sprint with id 1{noformat}

            h3. Expected behaviour
            The error should not be there and should just show that there is no issues found on the query.

            h3. Extra info
            The bug is only in GreenHopper 6.1.3.1. Tested in GreenHopper 6.0.8 and 6.1.2, the error does not persist.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSWCLOUD-7661 [ JSWCLOUD-7661 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-server fixme New: affects-cloud affects-server fixme
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: fixme New: affects-server fixme
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909370 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550692 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 747062 ] New: JIRA Bug Workflow w Kanban v6 [ 909370 ]

              Unassigned Unassigned
              znoorsazali Zul NS [Atlassian]
              Affected customers:
              2 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: