Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Bulk Change error

jira_admin_cu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
May 15, 2023

Hi Team,

When our users are trying to bulk-change tickets, they are always getting the below error. "users" and "jira-software-users" are already added to "Bulk Change" global permission.

Do any idea about this is an error on bulk change?

Log's referral number: 26d4a4ce-c5fa-4563-aaf7-941c422b237b

2 answers

1 accepted

1 vote
Answer accepted
Deleted user
June 24, 2018

Hi @Mohamed Adel,

Unfortunately Jira does not expose these values natively, however in a similar discussion users investigated the Script Runner add-on using the inSprint function. 

Jeff Curry, of Atlassian, mentioned using the advanced JQL functions openSprint() and closedSprint(). Though this will not display the exact dates of the sprint when querying issues. 

openSprints()

closedSprints()

Kristian Walker, of Adaptavist, has posted a script that should be able to give you a field for the sprint dates. If you need assistance with set up you should be able to reply to Kristian on the original post. He may be able to help you.

Hope this helps

Mohamed Adel
June 24, 2018

Thanks for your reply, 

Kristian's solution works for me. 

I added the scripted fields and now I can display them in the issue filter screen

Regards

0 votes
Chris Dennison
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 6, 2020

Seems like a custom field or two could be created to capture the assigned sprint's start and end dates.  Since Jira tracks multiple sprints for those tickets that roll over to later sprints, the function would have to take the latest dates.  I have the feeling this would still be tricky to set up since the dates may not be standard fields, plus it would need to accommodate if the sprint dates were changed or the ticket is moved to another sprint.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events