This is a quick feature overview for the Integratio of AgilePlan into Atlassian Jira. See the chapter Usage of the Atlassian Jira Plugin in our Documentation part for a detailled description. Use our Plugin for Atlassian Jira and find a complete toolchain for an issue based project management approach especially for Agile Projects. We can configure our tools to seamlessly integrate with Jira. Apart from the full licence you can still use one of the modules alone:
AgilePlan uses its own database scheme to save worklogs against booking categories (i.e. projects). This is the same when using the Jira Plugin. Still all produced worklogs are sent back to Jira, so keep Jira informed and in place for all its capabilities in project monitoring and reporting. The advantage of this solution is that AgilePlans meta-data system and budgeting system is in place and you are still able to use Jira.
Within the standard configuration of our plugin, in order to be able to track time on Jira sub-tasks, you have to start the progress on the subtask. However, you can configure almost any signal from Jira as the starter signal for Time Tracking.
Note that the 4x1 JIRA hierarchy (Project / Version / Issue / Subtask) is transferred into a 2x2 hierarchy in AgilePlans category tree (Project|Version - Issue|Subtask) to simplify the selection of the category you want to book on. At the same time, the User Assignment for AgilePlans booking category will be the Assignee of the Jira Ticket. So this guy will see the following dialog to choose issues to track time on them:
All time stamps will be transmitted to JIRA, also the remaining estimation will be updated automatically. So anything in Jira looks like time tracking would have done natively in this system:
After resolving an issue, you will not be able anymore to track time on it or even edit already booked entries.
In the time tracking overview these issues are grayed out.
As demonstrated so far, only the current assignee of a Jira Ticket is able to book times on the ticket. However we invented a Jira custom field - attendees - in order to let some co-workers in, to do teamwork. Our philosophy is to keep with the single assignee who should be responsible for the tickets overall estimation and his small working group.
After adding the attendee field to your Jira System you are able to assign attendees to issues.
All attendees assigned to an issue within Jira are also able to see the issue in the category chooser and are able to book time on it.
The AgilePlan category tree of Jira projects, versions, issues and sub-tasks can also be setup with metadata. So when creating a new project version in Jira, you maybe want to setup it with metadata like budgets or financial reference data before the team of the project is allowed to book time on issues in this project. Even more, you can choose to restrict Time Tracking to certain users no matter what the settings in Jira would be. To be able to do so, the project version must be activated manually in AgilePlan category hierarchy.
AgilePlan can help you in keeping track of "empty" remaining estimates. In Jira you can estimate remaining working time on every issue. For example you can estimate that the remaining work on your issue would take four more hours. Sometimes this estimated time doesn´t suffice and you have to book more than four hours on the issue. In this case a dialog will appear when you open your time tracking with this information.
If you want to know further details about this issue or directly increase the remaining estimate in Jira just click on the link and you will be redirected to jira immediately.
However our daily work showed as Reestimate anything before quitting as a good engineers pratice.
The "Estimation"-Button on the left side of the time tracking display will show all your tickets in progress in one dialog where you can enter your new estimations all at once. These estimations will also be modified in Jira.
Note that when using the weekly based time tracking interface, the current remaining estimation for categories transmitted from Jira is also shown in the rightmost column.