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

Project admin has an issue incorrectly added in his sprint and can't find which without a system admin

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Medium Medium (View bug fix roadmap)
    • None
    • None
    • None
    • None

      This issue has occurred a few times, and it's very devious. It can be very hard to impossible to diagnose by the project admins, and it's caused by a very simple error. Here's how it happens:

      1. User 1 is project admin in project A, but not in project B. He doesn't even have Browse Issues rights, so project B and its issues are essentially invisible
      2. User 2 is project admin in project B, but not on project A
      3. User 1 uses a Scrum board and starts a sprint
      4. User 2 reports an issue in project B. That issue's Create screen contains the Sprint field, but User 2 makes a mistakes: He manually types in the wrong sprint, and inadvertantly add that new issue to the sprint for project A
      5. User 1 attempts to close his sprint, but is met with a problem: He's not admin of project B. Since he doesn't even have Browse Issue rights, he's not allowed to see the name of the project this intruder issue belongs to.
      6. User 1 is smart and goes in Issues and filters for issues belonging to his sprint, but since he has no Browse Issues rights, he doesn't see the issue that's out of place.
      7. At this point, a JIRA admin has to get involved and must track down the problem. User 1 could not have found the problem, and user 2 couldn't have known about it until he was closing his own sprint and noticed the absence of an issue there.

      If user 1 had been project admin on project B as well, the sprint would have closed without errors, but this would have been a worse outcome. User 2 would have had an issue disappear from his backlog because it would be part of a closed sprint, and user 1 would have weird sprint reports.

      I see how this would be tricky to prevent. You would need a condition that "only issues that pass the filter for the board that created the sprint can be added to a sprint". Still, this seems like a huge problem area.

            [JSWSERVER-13444] Project admin has an issue incorrectly added in his sprint and can't find which without a system admin

            Yes, that's more like it. Thanks for your help!

            Nicolas Bourdages added a comment - Yes, that's more like it. Thanks for your help!

            Hey,

            Sorry for not understanding the problem correctly. We currently have an open feature request to provide the ability to restrict the sprints shown in the sprint drop-down. https://jira.atlassian.com/browse/JSW-10805.

            Please vote and watch on the issue to see its progress.

            Regards,
            Kiran

            Kiran (Inactive) added a comment - Hey, Sorry for not understanding the problem correctly. We currently have an open feature request to provide the ability to restrict the sprints shown in the sprint drop-down. https://jira.atlassian.com/browse/JSW-10805 . Please vote and watch on the issue to see its progress. Regards, Kiran

            Hi Kiran,
            That permission is good news, but that doesn't really help my current problem.

            The problem is that a user can add issues in a sprint that he does not "own" through the Sprint field.

            If I take an issue from project B, I can simply edit the Sprint field and select a sprint which normally contains only issues from project A. And just like that, I'm blocking the closure of that sprint, since the "sprint manager" from project A is not "sprint manager" for project B. JIRA wouldn't even tell me which issue is the problem, since I don't have Browse permissions on project B. I only get an error message that I can't close the sprint because an issue from project 1234155 (project B's ID) is blocking it.

            To fix that, there would need to be additional rules at the sprint level, something that means "Only people who have access to the board that created that sprint can add issues to the sprint." Or something to that effect.

            Nicolas Bourdages added a comment - Hi Kiran, That permission is good news, but that doesn't really help my current problem. The problem is that a user can add issues in a sprint that he does not "own" through the Sprint field. If I take an issue from project B, I can simply edit the Sprint field and select a sprint which normally contains only issues from project A. And just like that, I'm blocking the closure of that sprint, since the "sprint manager" from project A is not "sprint manager" for project B. JIRA wouldn't even tell me which issue is the problem, since I don't have Browse permissions on project B. I only get an error message that I can't close the sprint because an issue from project 1234155 (project B's ID) is blocking it. To fix that, there would need to be additional rules at the sprint level, something that means "Only people who have access to the board that created that sprint can add issues to the sprint." Or something to that effect.

            Hey Nicolas,

            In JIRA Software server 7.1.0, we have introduced Manage Sprint Permission. With this permission, there is no need for administer project permission to start or close a sprint.

            Regards,
            Kiran

            Kiran (Inactive) added a comment - Hey Nicolas, In JIRA Software server 7.1.0, we have introduced Manage Sprint Permission . With this permission, there is no need for administer project permission to start or close a sprint. Regards, Kiran

            That is totally not my name, some other poor guy got a confusing notification just now

            I'm using 6.3.15 server with Agile 6.7.11.

            Nicolas Bourdages added a comment - That is totally not my name, some other poor guy got a confusing notification just now I'm using 6.3.15 server with Agile 6.7.11.

            Hey admin821,

            Can you please let us know the version of JIRA and JIRA Agile/JIRA Software your instance has?

            Kiran (Inactive) added a comment - Hey admin821 , Can you please let us know the version of JIRA and JIRA Agile/JIRA Software your instance has?

              Unassigned Unassigned
              87a5880b5bd3 Nicolas Bourdages
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: