Using our JIRA integration, you can import your tickets from JIRA into the Accelo platform!
Using this guide, you can:
Understand what JIRA links to in Accelo
Our JIRA integration can link to a multitude of objects within Accelo. It may be intimidating to think about what the best thing to link them to would be, so we break down some common use cases here:
- Milestones - Link your JIRA tickets to Milestones when the work is part of a larger Project. If your Project depends on multiple JIRA tickets to finish your work, it's good to place them against milestones.
- Tickets/Issues - A direct 1-to-1 ratio of one ticket to one JIRA. This is the most common type of link that is used.
-
Projects/Jobs - For your larger JIRA tickets to link to, such as Epics. We recommend linking your JIRA Epics (that is comprised of many smaller JIRA tickets) to the Project level.
- Retainers/Contracts - Have JIRA work that is covered by an ongoing contract? You can link it directly to one in Accelo. Although putting it to one of the work items above and having them link to the Retainer can also work.
In all the examples above, when a JIRA ticket is linked, a Task will be created under the associated object. This is where we pull in and sync the associated work.
Connect JIRA Tickets to Accelo Work
An admin user must first connect to JIRA prior to other Accelo users. Each JIRA user must download the Accelo Extension. Of course, your Accelo account must've completed the JIRA integration as well.
To connect a JIRA TIcket to Accelo Work:
-
Create a JIRA Ticket within JIRA.
-
Make sure your Configurations at the top right include the Accelo field.
-
Complete your required fields, and locate the Accelo field, which should look like the image here.
-
Search for the object in Accelo you'd like to link it to, and save.
-
Once linked, you'll find the details and breadcrumbs of the Accelo object in your JIRA ticket details. This will allow you to access the Accelo related work very easily in the future by clicking on it when you're working on the ticket in JIRA.
-
A Task will also be created under the associated work object in Accelo. A JIRA link badge will be available on the Task to quickly go to the associated JIRA ticket.
Once the above are completed, your work details from JIRA will automatically sync into Accelo to the users mapped in your integration.
Link JIRA Epics and Their Issues to Accelo
JIRA Epics are a great way to group together multiple, related Issues. These Epics can also be linked to Accelo as a quick and easy way to link all of their Issues to Accelo.
When an Epic is linked to Accelo, the Epic does not create a corresponding Task in Accelo. Instead, the integration will:
-
Automatically create a corresponding Accelo Task for all Issues which are currently linked to the Epic, but have not yet been linked to Accelo.
-
Automatically create a corresponding Accelo Task for new issues which are linked to the Epic moving forward.
Linking a JIRA Epic to an Accelo Project or Milestone is a great way to ensure that all of your work in JIRA is automatically synced with Accelo for accurate billing.
Sync Comments and Work Logs
You are able to have Comments or Work Logs in JIRA push over to your different objects within Accelo (Projects, Milestones, Tickets and Retainers). This will allow you have your tasks in JIRA coordinate with (possibly) billable budgets within Accelo.
When you log Comments and Work Logs in JIRA, that will pulled into the linked/created task within Accelo that sits under the respective Object (Project, Milestone, Ticket, Retainer) within.
For each object, there might be a similar but different effect (you’ll notice verbiage below is similar).
-
Project / Milestone
-
Project: If linked, you would have a task directly against the Project. This will bring over Comments and Work Logs and log it at the rate and against budget for the overall Project.
-
Milestone: If linked, you would have a task created within the Milestone. This will bring over Comments and Work Logs and log it at the rate and against budget for that given Milestone which may roll up to the overall Project.
-
-
Tickets:
-
Non-Billable Tickets: You can link a JIRA Issue to a “No Rate” ticket. This essentially, will be looking to track the time it took to complete and close out the Ticket. You can also track the Staff Costs for this.
-
Billable Tickets: If linked, you would have a task created directly against that Ticket. This will bring over Comments and Work Logs and log it at the rate and against budget for that given Ticket.
-
-
Retainers
-
Pre-Paid: If linked, you would have a task created directly against the most recently opened Period. This will bring over Comments and Work Logs and log it with the billable rate and time for the given Period.
-
Post-Paid: If linked, you would have a task created directly against the most recently created Period. This will bring over Comments and Work Logs and log it at the rate and against budget too add to the billable value of work to be billed at the end of the Period.
-
We do not recommend using both the Accelo integration and time management plugins like Tempo.
These integrations create all work logs in JIRA on behalf of a single user, rather than the user who actually logged time, meaning that all work logs will sync with Accelo on behalf of a single user.
How to Invoice JIRA Work
Essentially, these JIRA Work Logs and Comments can be billed like Accelo Activities are. You’d use the same invoicing tools, including Client Billing. Luckily, we have help pages for all of them!