We need to have a higher resolution on the information captured by toggl from JIRA.
This could be by capturing the parent EPIC that a JIRA story or task belongs to, or by capturing a specific field content that we would add for his purpose, so that we can correctly bill hours to different work packages within a project.
Is there any way to capture an extra resolution of data into Toggl beyond the base JIRA ticket number / project
Greatly appreciate your thoughts on this, we want to get all the value we can from the two systems.
We're trying to do the same thing, we use components for splitting the work and epics for overarching stories (projects) that encompass multiple components. Either way would be nice, using an epic might work, but we'd have a huge list of epics to track when using an agile work board between multiple projects. This is why we favored components.
With joggler you have to ways to achieve this:
On the toggl configuration page in JIRA you can mark your Epic issue type as a project tracking issue type. For Each epic you can then create a separate project in Toggl and all work that belongs to the Epic is then tracked in the corresponding project.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG