Given that Bitergia uses Confluence usernames in its data import process to identify authors (and as a result of that, we store this information in our person metadata), it seems safe to assume that they will be impacted by this change, and that by extension we will be impacted too.
This JIRA issue involves:
Working with Bitergia support to understand how this change impacts the user identity file we currently send them
Updating all Confluence usernames in the metadata repository to ensure they're in sync with whatever new identifier Bitergia is using in place of Atlassian usernames
My guess is that Atlassian are moving to using email addresses to identify users, which should (hopefully... 🤞🏻) mean that we're minimally impacted (given we already record email addresses elsewhere in the metadata).
It's possible that this will require updates to the person metadata schema (e.g. to remove the confluenceUsernames property if it becomes redundant).
Side note: remember to roll a new schema version if such changes are required and they're not backwards compatible.
Fixing any fallout from any of the above activities that impact the metadata-tool (e.g. if Confluence user names are removed from Bitergia's identities YAML file and/or our person metadata schema)
Acceptance Criteria
None
Activity
Show:
Maurizio Pillitu
January 16, 2020 at 12:08 PM
We eventually worked around Confluence user API; all metadata builds are working now, closing issue.
High
Atlassian have recently announced that they will be removing usernames from both the Confluence administration UI and the APIs.
Given that Bitergia uses Confluence usernames in its data import process to identify authors (and as a result of that, we store this information in our person metadata), it seems safe to assume that they will be impacted by this change, and that by extension we will be impacted too.
This JIRA issue involves:
Working with Bitergia support to understand how this change impacts the user identity file we currently send them
Updating all Confluence usernames in the metadata repository to ensure they're in sync with whatever new identifier Bitergia is using in place of Atlassian usernames
My guess is that Atlassian are moving to using email addresses to identify users, which should (hopefully... 🤞🏻) mean that we're minimally impacted (given we already record email addresses elsewhere in the metadata).
It's possible that this will require updates to the person metadata schema (e.g. to remove the
confluenceUsernamesproperty if it becomes redundant).Side note: remember to roll a new schema version if such changes are required and they're not backwards compatible.
Fixing any fallout from any of the above activities that impact the metadata-tool (e.g. if Confluence user names are removed from Bitergia's identities YAML file and/or our person metadata schema)