Hi Atlassian Community,
Weβre in the process of planning the removal of BigPicture from our Jira Cloud instance. While we have considered alternative solutions for some functionalities, weβd like to validate our understanding of the potential impact and ensure a seamless transition.
Here's what we've planned so far:
Workflows: We suspect that workflows may be impacted if any BigPicture-specific configurations exist.
Screens and Fields: Similarly, weβre concerned about any custom screens or fields tied to BigPicture use cases.
Gantt Charts & Hierarchy (Data Transition): We plan to transition Gantt chart management to Jira Advanced Roadmaps (Plans) and implement a new hierarchy in Jira to support this.
- Any advice on structuring a clean hierarchy during migration?
Dashboards: Weβve accounted for creating new dashboards at each level to replace those impacted by BigPicture.
Permissions and Roles: Our plan includes modifying or creating new groups and roles to handle permissions adjustments after BigPictureβs removal.
Lastly, weβd like to confirm if there are any risks we might be overlookingβespecially regarding automation rules, linked data, or other system dependencies.
Any shared experiences, recommendations, or best practices would be greatly appreciated as we navigate this migration!
Thank you in advance for your insights!Β
Eduardo
Β
