nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bulk transition without changing updated date?

Philip Winston

I'm adding some PM related statuses to our workflow. I'm going to bulk edit my Open issues into a new status called Hold, and then drag a few back to Open in Greenhopper. Is there a way to do this without touching the updated date? If someone queries for issues updated in the last 7d or 30d I don't want them to think that everthing was updated. I don't want this one move to count as an update, I want update to refer to a normal user changes.

Accepted answers

All comments

Nic Brough -Adaptavist-

No, you can't do this. Jira is designed to track changes to issues, and you're making changes, so it logs them

I think you might be able to write a plugin that provides a post-function that updates the date after a transition (which you'd probably want to protect so that only admins can use that transition). If you do that, it will still write to the history, and then you could well get questions on why the updated date is wrong.

Kai Gottschalk

Hi Philip,

I guess I have a potential solution for your problem. It is not via bulk change (as you asked for), bit via .csv-import, where you can - besides creating issues - update them as well, see JIRA docu.

I'd recomend to draw - via advanced search - a .csv/excel-export of the affected issues containing only three fields: "Issuekey", "Status" and "Modified date". After changing the status of the issue as required, you can import the data via the "Import external projects"-function.

Disclaimer: Not what you asked for, not tested, and as well a bit manual work, but should most likely lead to the desired result.

Curious to receive your feedback!

Cheers
Kai

Philip Winston

Very interesting I might try this. I thought of another option in our case. We have 1000 Open issues and we want most all of them to be Hold now, where we move just some to Open. How about when we edit the workflow, we turn Open into Hold, then introduce a new Open, wire it all up how we want, seems like that might work if it lets you rename a status without affectings it's underlying ID. Might experiment with both ways.

Randall Robertson

Do you have any other workflows that also use this Open status you are considering renaming? Changing the status name affects all workflows that use that status.

Philip Winston

Oh good call. This is the only really active project, but still that feels weird to rename them Open to Hold for the dormant project and all future projects. Maybe the CSV export is the best idea, I'll try it.

Sanu Soman1

Is this possible by csv import?

Sanu Soman1

Is this possible by csv import?

Ann Kristin

You set a date for "date modified" if importing by CSV, yes.
(Now I see that it is already answered and an old question, sorry.)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration