Update History Entries

  • ewest
Posted: Tue, 01/10/2012 - 12:19

We have a fairly large JIRA installation
Currently when Updating the History Entries I am faced with the option of selecting a "Corresponding Custom Field" which does not make sense at present.

Are you mapping all the Fields to a unique custom field (Must we perform this action).
Currently the system states -- Displaying first 1000 of 123065 entries.

Can we not map field via a config file or unselect what we dont want?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Increase tempMax value

  • admin
  • 02/16/10
  • Mon, 07/16/2012 - 10:36

Hi Earl,

Unfortunately, I can't suggest anything better than increasing tempMax value to see more history records and therefore be able to update records past the deleted ones. By the way, what version of JFS do you use? Possibly I can make an update for you with a 'skip' option.


History Update - What do you do with the deleted custom fields

  • ewest
  • 01/09/12
  • Fri, 07/13/2012 - 17:01

We are attempting to work our way through the History Update a 1000 records at a time. There are a number of deleted custom fields that we don't care about protecting/updating because they are deleted. But there seems to be no option to skip? And now I have 1000 issues with deleted fields that is filling up my screen. There doesn't seem to be a next page option?
Frustrated. HELP....

This question has been

  • admin
  • 02/16/10
  • Wed, 02/01/2012 - 20:22

This question has been answered via e-mail. I'll copy and paste an answer here to share it with other users.
You should perform this update only if you wish to protect existing history records (i.e. changes for existing fields). This operation is needed because JIRA originally does not store field ids in history but only field names.

If you still wish to update change history records, you may try to change tempMax parameter in URL, e.g.: from http://host/secure/admin/FieldIdUpdate!default.jspa?tempMax=1000 to http://host/secure/admin/FieldIdUpdate!default.jspa?tempMax=10000

Please be careful changing tempMax - too high values may cause your browser and/or JIRA appserver to consume too much memory and slow down the whole system.