No answer from Atlassian, well can’t say I’m surprised. May I suggest a change to the company moto: Open Company, No Bullshit (unless one or more parties mention account id migration and data stored in workflows)
A bit wordy but it may catch on
1 Like
@paul - I’m not sure what your question was from that previous post. Yes, you may still have workflow post functions containing usernames after the deadline. The new migration API is meant to alleviate some of that pain by facilitating lookup post the deprecation date. We need to work out how to migrate historical configurations from old user references to accountID for apps that store data in product. Ideally, when your app is ready, users can re-save their configurations to use accountID references instead of username, like we’re doing with JQL queries and the ‘PD cleaner’. Do you think that will work? (and if so, what support would you need and when?)
Hi @akassab, thanks for replying. I’m in the process of migrating all my apps to account id at the moment. The migration (of which one is already completed) will do everything except the workflow. If a workflow event occurs then any non account ids are converted and processed as account ids using the normal user REST API. If a user edits and saves the workflows then they are automatically converted.
A couple of questions:
- Since the user REST API is going to stop working in April I assume I should be using the migration API. I couldn’t find this migration API, could you please post a link
- I assume that once I convert everything except the workflow that Atlassian is happy for me to set the “App Stores Personal Data” to No. Is this correct?
- Is Atlassian looking at possible doing anything to migrate workflows?
Thanks
Paul
@akassab, Can you answer these questions. Sorry to sound pushy but I’m trying to migrate to account ids and I need answers.
Thanks
Paul
@paul - No problems, happy to help. I thought these were already addressed in the items in progress section above but after further review I realize only question #1 was already addressed.
Please leave as “Yes” for now. We need to be able to identify apps that have stored historical user references which haven’t been migrated due to known blockers for clean up activity.
We have been looking into providing an API to facilitate the editing of Jira Workflows, however I do not have confirmation yet from the Jira team on whether or not that API will be available before the deprecation date. The migration endpoint referenced above should facilitate translation of Jira Workflows using historical user references without that API.
Hi @akassab, thanks for that. Regarding the answer for question 2 how will you know who hasn’t migrated due to blockers and who is still to implement the REST API?
Also can someone remove the user data REST API question for server plugins. My understanding is that this is cloud only but still appears for all server plugins.
Thanks
Paul
To keep everyone pointed to the latest status update we’re going to close this topic to discussion. We’ll do our best to address any open questions in this weeks status update.
Thanks for your understanding.