Skip to main content
T
tmiller-31-Visitor
1-Visitor
June 7, 2016
Solved

How can I make one change to multiple requests? Mass update?

  • June 7, 2016
  • 3 replies
  • 5272 views

As an example, we have 10 existing change requests. I would like to input the words "Project 1" into the summary or title of each without opening each individually. Anyone know of a process to do that?

Best answer by MichaelChatel

Hi Ty,

You can "batch edit" from within the Integrity GUI client.  If you check the Integrity user guide, for your version of Integrity, search for "Batch Editing Items".

You simply multi-select the items you want to edit from your items view, and Pick "Edit Item" from your Edit menu in the client.

Also, depending on your scenario, you could probably write up a CLI command as well, but batch editing is available from within the GUI client.

3 replies

M
MichaelChatel5-Regular MemberAnswer
5-Regular Member
June 9, 2016

Hi Ty,

You can "batch edit" from within the Integrity GUI client.  If you check the Integrity user guide, for your version of Integrity, search for "Batch Editing Items".

You simply multi-select the items you want to edit from your items view, and Pick "Edit Item" from your Edit menu in the client.

Also, depending on your scenario, you could probably write up a CLI command as well, but batch editing is available from within the GUI client.

K
khoppe15-Moonstone
15-Moonstone
June 10, 2016

Batch Edit like explained won't work with a text field which shall get additional content like described.

For this use case I suggest to use Query Result view with Option "Table Content  ==  Editable".
Then you are able to do the requested change in the list.

Batch Editing is more practicable from my perspective for Fields of type   Pick, State, User,

AND  if you have text fields with option  logging.
Reason: Multiple edit will exchange  (= overwrite) existing  existing entries with new chosen content.

K
KaelLizak16-Pearl
16-Pearl
June 10, 2016

Hello Ty Miller, Klaus Hoppe‌‌, and Michael Chatel‌,

Klaus Hoppe‌ is right.  I'm assuming the goal here is to not have to edit the fields by hand, as opposed to trying to get the edits to all have the same timestamp.  For text fields, the easiest approach to get something like a batch edit would be to create a batch/shell script (depending on the client platform), fetch the value of the field to be edited, and then add the text in the appropriate way to the field.  Assuming rich text, and assuming you're appending text to the existing contents, you'd probably use these steps:

  1. im viewissue --showRichContent --batch <issueID>
  2. Parse the output of step 1 to get the relevant field's contents
  3. im editissue --richContentField=<RichContentFieldName>=<OriginalFieldContent>+<NewContent>
    <RichContentFieldName> refers to the actual name of the relevant field, and <OriginalFieldContent> refers to the contents of that field, both from step 2.

I hope that helps.


Regards,

Kael


J
jbates-21-Visitor
1-Visitor
June 10, 2016

Klaus is quite correct. The bulk edit for plain text fields is an overwrite. You can't "add text" to the field, simply replace it. If replacement is what you're after, bulk edit is your best bet. If you're looking at add text, you'll need a script for that, and the edits would be done individually.

What's the reasoning behind editing in this manner? Is this to make the edits easier for users? Or looking for some sort of performance improvement? Keep the updates atomic, so that if any one fails they all fail?

Personally, I think that an enhancement request is in order. Something that will perform either a recursive or non-recursive field replacement on the edit value. For example, if you were to bulk edit the Summary field, with a non-recursive update, you could use replacement text of:   Project 1: {Summary}   which would prefix the original value with the static text.

Yep, I smell an enhancement request coming any second now...

K
KaelLizak16-Pearl
16-Pearl
June 10, 2016

Hi Jim Bates‌,

I completely agree.

Ty Miller‌, you can find the Ideas/enhancement request section here.

Regards,
Kael

T
tmiller-31-VisitorAuthor
1-Visitor
June 10, 2016

Everyone provided fantastic feedback. The first answer worked for what I was doing. I am frustrated for not realizing that it was that easy. Sigh. Anyway, thanks to everyone for their input. This conversation was definitely fruitful for me.

Terms & ConditionsCookie settingsAccessibility statement