Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I bulk update priorities without changing updated date?

Currently the team has way too many tickets assigned to individual team members and has not been given attention for a long time. These tickets have grown in size over a period of time. Team would like to bump the priorities of all existing ticket by 1 (eg: P1 to P2, P2 to P3 and so on) without modifying the updated date and then assign the tickets to be worked on with P1 during the next planning session.

 

Is there a way to bulk update all ticket priorities in a project without modifying the updated date?

2 answers

2 accepted

1 vote
Answer accepted

You can't do this without a database hack, you'd be lying about the updated date, and that's not what an issue tracker is for.

However, there is a sneaky trick you could play.  Go to the priority scheme and add a new priority called (say) P0.  Now rename p3 to p4, p2 to p3, p1 to p2, and then p0 to p1.  Everything will go down a priority level without actually changing.  You can delete the lowest level priority, Jira will offer to change issues in it to another level (this will change the updated date though, but are you really that bothered about that on the very lowest priority issues?)

0 votes
Answer accepted

Hi @Raju Alagappan,

Theoretically you could do that by running updates directly in the database. But I don't think anyone would recommend doing something like that for I don't know how many good reasons.

If your goal is to bump the priority to P1, assign the tickets to be worked on and - in a next planning session probably assigning them to an upcoming sprint? - knowing the updated date may just help you facilitate the planning session. The other changes you are planning to do will update the updated date anyway. Suppose you update them tomorrow, you can easily retrieve them with a filter like this:

Priority = P1 AND Priority changed on 2020-12-08 

I would strongly recommend to use built-in bulk change functionality to perform the update.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

4,562 views 12 8
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you