How update a list of items to push the data to Jira

[#1]

Summary

There are some scenarios where changes can exist in JA and not be pushed to Jira (like a problem with the connection, or a name change on the PI) and an update may be needed on JA to push these changes. Below, we will discuss some possible ways to do that.

Solution

Once an update is made on JA, be it through the UI, API, or Import, it will mark the entry as to be pushed to Jira, so these are possible ways to accomplish it for multiple items.

API

To use the API to do this, it would be possible to do a PUT or a PATCH on an item, or list of them, to mark them as updated. One possible idea is to add a tag on it, to mark the work item.

If using PATCH, a similar syntax could be used to create a tag on the item:

If the only tag present is the one added by the connector (with the “j:”), it will be overwritten but this command, but on the next cycle, re-added. Now, if there are multiple tags, you will need to use as a value, the entire list of tags adding the new one if you want, to avoid losing any of them.

Or, if you don't have the Priority set, you can update it from null to null:

In case there are multiple items to be updated, some sort of automation should be used to control the API calls to all the items.

Export/Import

It is possible to export the impacted items and do an import in the sequence, without altering the data. This will trigger JA into “seeing" an update on them and marking them to be pushed to Jira.

To do the export:

1. Set the Config bar to display the data you want (like Program + PI)

2. Go to the desired grid (Features/Stories)

3. Click on More Options > Export <work_item> > click on the export button

To import them:

1. Set the Config bar to display the data you want (like Program + PI)

2. Go to the desired grid (Features/Stories)

3. Click on More Options > Import <work_item> Select the Program > Browse (to select the file) > Import Data

You can also alter the exported data, like adding a tag to all entries, to make it easier to track later on which items were updated this way.

Mass move

It is possible to use the Mass Move option to “move" items between the current Program + PI, to the same Program + PI, which will trigger an update on JA, and push them to Jira.

To use the Mass Move:

1. Set the Config bar to display the data you want (like Program + PI)

2. Go to the desired grid (Features/Stories)

3. Click on More Options > Mass Move

4. On the MOVE FROM section, select the desired work item type, the current Program, and Program Increment

5. On the MOVE TO section, select the same Program and Program Increment

6. Mark all the items you want to update and click on Save Changes

Manual Update

Last, but not least, if you are working on a small list of impacted items, you can simply do a manual update on the UI, to force them to be pushed to Jira. In this case, just open the slide-out panel of the item, add a “." to the description, and hit save.

[Isabelle Lehodey]

Thank you for this article @Victor Fragoso .

Is there an easy way to tell if some changes or items have not been pushed to Jira?

[Colin Weaver]

This community article (which was written by Atlassian Technical Support) has now been reproduced in the Jira Align Knowledgebase (KB) . This has been done in order to allow more flexibility for any possible future updates or corrections. Please be aware that the KB version available at the below link may contain the latest information:

How update a list of items in Jira Align to push the data to Jira

For more information on the launch of the Jira Align Knowledge Base go to:

Jira Align Knowledge Base Announcement