Upgrading to 2.4.0 from 2.3.2

Prior to 2.4.0 release, functional users were possibly associated directly to consumers, for accessing Jira TRS feeds. When upgrading to 2.4.0 release, a migration is automatically executed for consumers to use a unique TRS functional user instead. If functional users were associated to consumers, it is recommended to verify the migration was successful:

1. Enter the Consumers page.
   1. Enter the JIRA ADMINISTRATION > Manage apps page.
   2. On the left panel, click the Consumers option in the OSLC Connect section.
2. Look up for the consumer you had previously associated to a functional user ^[2].
3. If the Functional User column now looks like Tracked Resource Set (<previously_functional_user>), means migration was successful and you are done with upgrading actions; otherwise, if you only see your previous functional user, keep reading.

If migration failed, possible reasons are:

• Multiple consumers were associated to different functional users.
• Migration process raised a database/system failure.

Before manual migration steps are explained, make sure all consumers that require a functional user are indeed associated to a unique functional user. If different functional users were used, you will have to decide among them which one will be the unique TRS Functional User. You may still define different consumers for different TRS consuming applications (like LQE or LDX), but starting with this release all of them must be associated to the same TRS Functional user.

Once you have decided which Jira user will be the final TRS Functional user:

1. Follow the steps of the Assigning Tracked Resource Set Functional User procedure to assign the chosen Jira user as the TRS Functional user.
2. In the consumers page, and for each associated consumer, follow the steps of the Updating a Consumer procedure to associate them to the TRS Functional user.

^[1] If IBM Engineering Lifecycle Management global configurations or IBM Jazz Reporting Service / IBM Engineering Lifecycle Optimization - Engineering Insights (ENI) are being used by any Jira project administrator, advise the IBM Link Index Provider (LDX) and IBM Lifecycle Query Engine (LQE) administrators to verify the Jira datasources and to re-index in the case an error status was reported after the upgrading. This is a very important task in order to keep synchronizing those applications with Jira. On Reindexing an LDX/LQE datasource topic, LDX/LQE administrators can find a guide to do it. ^[2] If you had configured more than one consumer to a functional user, next steps apply for all of them.