Playbook | Jira/DevOps Integration Enhancements

Jira/DevOps Integrations

1. To familiarize yourself with previous What's New articles on this topic, refer to the following...
   1. Playbook | Integration with DevOps - MVP1
   2. Playbook | Integration with DevOps - MVP2
   3. Playbook | Integration with Jira - MVP1
2. Now, when setting up the Connector, you specify the project to pull from rather than providing a URL with it embedded somewhere in the URL.
   
3. Now, after the first pull for new Connectors and after the next pull for existing ones, you will see a "link to the item in Jira/DevOps" in Task Properties. When you click the link, Jira/DevOps opens in a new browser tab and shows you that item.
   
4. Now, epics and any other type of externally connected item with a child are created in Playbook as an External Summary task.
   
5. External Summary tasks behave the same as other Playbook Summary tasks.
   
   1. Have an Owner, but no Resources.
   2. No hours of Work (hours in a summary are the summation of all hours in their subtasks).
   3. Duration can be set manually or auto-sized.
   4. Default Calendar (Weekdays duration units)
   5. Auto-complete 
   6. Expand/collapse icon is in the External Summary's taskbar.
6. All other types of externally connected items (non-epics with no children) are created as External Work tasks.
   
7. External Work tasks behave the same as regular Playbook Work tasks.
   1. Assign Resources
   2. Hours of Work (used in resource loading etc.)
   3. Resource Calendar (Working Days units)
   4. Managed in the calendar and backlog in the Huddle and My Playbook views.
   5. Indicated by an icon to the left of the task's title like Meeting and Monitor tasks.
8. When a task was started as an External Work task, then a child is later added to it in Jira/DevOps, the next time it is pulled/updated via the Connector, it is automatically converted to an External Summary task.
9. Where applicable, users can change a task's type (External Summary/Work) using Task Properties or the Task Grid.
   
   
10. Now, external tasks can have predecessors to/from all other tasks in the plan.
    1. The color of the external tasks automatically changes to show their criticality (yellow, orange, pink) like all other Playbook tasks.
11. Subtasks can be easily created in External Summary tasks.