[jira] No way to adopt an identity

Labels: lifecycle/rotten

cheshirekow (cheshirekow) opened

In summary of our gitter discussion: With the new credentials system, there is no way to adopt an JIRA imported identity. The credentials that are created are associated with an identity that git-bug itself creates and there is no way to re-associate them after adopting an identity.

@MichaelMure said that there should be an equivalent of git bug bridge auth add-token for login/password credentials.

cheshirekow (cheshirekow) changed the title from [jira] No way to adopt an identity to [jira] No way to adopt an identity

Michael Muré (MichaelMure) commented

That would be https://github.com/MichaelMure/git-bug/issues/336

That command would accept the credential as well as a user ID and the bridge login. It would then tag the user with the correct login metadata (the bridge expose the correct key to user).

This would solve this problem but it's not perfect either. I think we might also need a way to either:

  • associate an existing credential to an existing user
  • tag an existing user with a login for a specific bridge

It's almost the same thing but framed slightly differently. This might be part of those add-xxx commands or a different command, or even all of those merged into one.

github-actions (github-actions) commented

This bot triages untriaged issues and PRs according to the following rules:

  • After 90 days of inactivity, the lifecycle/stale label is applied
  • After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

  • Remove the lifecycle/stale label
  • Comment on this issue

github-actions (github-actions) added label lifecycle/stale

github-actions (github-actions) commented

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

  • After 90 days of inactivity, lifecycle/stale is applied
  • After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

  • Remove the stale label from this issue
  • Comment on this issue
  • Close this issue
  • Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/rotten

github-actions (github-actions) removed label lifecycle/stale

sudoforge removed label lifecycle/dormant