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:
JIRA ADMINISTRATION > Manage appspage.
Consumersoption in the
Functional Usercolumn 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:
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: