Hi, I'm working on a query where the user can see their tickets in projects where they are authorized-to, and recurring efforts in some specific boards. I'm using the following query:
project in projectsWhereUserHasPermission("Browse Projects") AND status in ("In Progress", Testing, "To Do", "Recurring Effort") AND Sprint in (openSprints(), futureSprints()) AND assignee in (...) ORDER BY originalEstimate ASC, key ASC, status DESC, summary ASC, assignee ASC, priority DESC, updated DESC
But the issue is that it fetches all the future sprints, and I only want to fetch an specific (e.g. sprint 1057, sprint 345, etc...)
Is there any way to workaround with the query I have?
Hi @Daniel J. Alvarez Galo and welcome to the community,
For starters I would ditch completely the "project in projectsWhereUserHasPermission("Browse Projects") " and keep only the rest:
status in ("In Progress", Testing, "To Do", "Recurring Effort") AND Sprint in (openSprints(), futureSprints()) AND assignee in (...)
Keep in mind that due to permissions, by default users are able to see only tickets that are eligible to see. Now, it is not clear to me as to which issues these users must see. If e.g. they only have to see the issues to which they are assignee, then I would simply add the assignee=currentUser() to your JQL. This would only bring the sprints to which that specific user would be the assignee and not all sprints.
Is that what you had in mind or I didn't get your question correctly?
Hi @Alex Koxaras -Relational- and thanks a lot for your response.
The assignee in (...) contains the account_id of a user (e.g. 453edgsf3). The motif for this is that admins want to see which tickets my colleagues have in order to check who can take a specific task (according to their ticket payload) and only in the projects where they are included. I tried to use the assignee=<assignee_name> and works nice as well.
Now the intention for the specific boards is that I manage some boards that are "relevant" or "recurring effort boards" and I don't want to check every time a sprint is active, closed or relevant, just fetch the data automatically with the settled parameters as well as specific "recurring effort boards".
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.