I would LOVE to get advice from people who've integrated Jira and Workfront successfully for their teams. 1-1000+ users Sinnaps is ideal for small and medium enterprises that need to plan projects to organize and prioritize their work.
Currently, eight or nine reports are there. I would like to have more reports in Jira. Being able to define access based on the roles will give us more flexibility in managing Jira. Currently, anyone with Jira access can access everything. when a Jira ticket is closes, it marks the Workfront task as complete - the link to the Jira ticket is accessible directly from the task. Jira Service Management is primarily used as a service solution, from asset management to DevOps. Enterprise teams and departments (not just project managers) that need to manage all their work (waterfall, Agile, or otherwise) in a single, smart, connected location. Integrating work management solutions like Workfront and JIRA is a critical step towards streamlining workflows and improving efficiency for businesses. This is something that Jira can look into. We've looked into the Workfront/Jira integration, which allows you to generate a Jira ticket automatically when a task is assigned to a specific user, but we're seeing a few limitations so have not implemented it: - every WF task assigned to that designated user will generate a Jira ticket, but we want only 1 master Jira ticket per project, not individual Jira tickets tied to each tasks - comments from Jira don't ladder-up into Workfront - comments and info from Jira sub-tickets (under the master ticket) don't tie to the Workfront project. Hi Wendy, thanks for raising this! Same here, our developers use Jira for dev and QA tasks for 2 reasons: - our QA team is offshore and does not use Workfront - we don't find Workfront's structure adapted for dev/QA ticketing.
0 kommentar(er)
