Custom API Integrations: Integrators should expect to use custom API calls for certain objects such as “statuses,” as native Fusion connectors do not support certain objects.Stakeholder Management: Identify and communicate with all stakeholders and teams affected by the automation in both systems to prepare and inform users of the change.Clearly identify which Workfront and Jira objects will be impacted (ex. Align key transition values between Workfront and Jira teams such as “Status” and “Priority” to maintain a uniform experience. Field & Object Mapping: Ensure all Workfront fields are mapped properly to the Jira production environment custom field values.What Workfront Users Need to Know About Jira Before Integrationįuture integrators should take the following steps to ensure a smooth process: Marketers and engineers have big picture view of project status.Ĭonnecting the leading work management platform marketers count on (Adobe Workfront) with the project management software developers need (Jira) results in a smooth operations environment that lets teams drive work forward, together.Marketing and tech pros provide input (status, hours spent, etc.) simultaneously.Marketing team member makes a request in Workfront, and it’s automatically made in Jira too. Members of both teams have limited visibility into project status.Entering data twice increases risk for error.Marketing team member makes identical requests in both Workfront and Jira to activate a project. The Adobe Workfront platform now automatically connects to Jira’s projects and tasks-so workflows are synced, work is completed faster, and the work experience is enhanced.
Create a Seamless Experience From Every Point of View The result? A synchronized, efficient experience that gives marketing leaders real-time insight into the status of projects and associated technical tasks. Zee Jay’s digital ops experts worked shoulder to shoulder with the client for an automatic, bi-directional integration between Adobe Workfront and Jira.
0 kommentar(er)
