Hi,
A colleague of mine is trying to manage sprints for a particular board (Let's call it XY-board).
XY-board has a filter that specifies 2 different projects, and a specific label used in only one of the projects.
My colleague has 'Manage Sprints'-permission for both projects (he is project administrator, who has that permission).
The query used to filter the issues in the board is as follows: project = X OR project = Y AND labels = A ORDER BY Rank ASC
This query is "complex" and as far as I understand this, is why he is unable to manage sprints for this board. However, I tried stripping down the query until it was just: "project = X or project = Y" and this is still considered complex.
Therefore, two questions:
Thanks and regards,
Martin
1: your question is not complex, i have tride the exact same, and the ORDER BY Rank ASC, i had to add in the advanced mode, then i can get it back to basic.
2:Check the permission scheme for both projects and see if the user has the right to manage sprints, and transition issues.
Hi Tomas,
Thank you for helping.
Just FYI, we are running 7.11.2
1. Jira is flagging it as complex until I remove the 'OR' keyword. I tried creating the query in Basic, but choosing both projects in the project field, will of course form the query as follows: "project in (X,Y) and labels = A".
This will only return issues from project Y where label = A (label is only active for project Y), thereby omitting issues from project X. This is not the desired outcome.
2. I have checked both permission schemes, and the user has both 'manage sprints' and 'transition issue'-permission for the projects in question.
Thanks and regards,
Martin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1. yes that's true, why does it matter for you if you query is advanced or basic?
2. That's good, how is the board that he is using shared? and what roles are set to manage sprints?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
2.
First when you configure the board you can filter what you shall see on the board.
Then you can choose who are allowed to see that board, e.g all user with in the project x or within project x and y. Or a certain group of users and so on.
Then
I mean that a project it self has permissions that are given to a project role or group of users.
Then you also have a setting for users and roles, just under permissions in project settings, you can change these settings if you are a jira admin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.