How are people handling archiving Shared Teams?

Erin Quick-Laughlin
Contributor
October 21, 2022

We recently moved everything over from a custom field to the Team[Team] field, or Shared Team, available through Advanced Roadmaps.

In the past, if we wanted to archive a team, we simply disabled that option in the custom field, and any issues with that option kept their data, but going forward, no one could add that team to an issue.

Now, we expose the Team[Team] field on the issue, as well as using in AR of course, but our only options seem to be:

  • Delete the Shared Team: which would remove it and the associated ID, and no longer be available on historical issues.
  • Rename the Shared Team: we are currently adding "archive" in some format to the name, so that filters and external reporting systems can ignore them.

 

Anyone have a more effective or elegant solution to this issue that they could share?

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events