Allstacks pulls tickets, cards, stories, and other units of work from your project management tools such as Jira. We combine that with data about deliverables and milestones such as releases, epics, initiatives, and projects and activities such as estimation changes, completions, comments, and status updates to provide a very comprehensive picture of your work.
Allstacks service connection to Jira is established either via an API Token or OAuth. For short-term trials, we recommend using Jira(Basic) to connect using API token for ease of use. For production setup, Jira (OAuth) is preferred longer term.
Jira (Basic) - Connect using API token
Before starting, confirm that you are actively signed into Jira with the account, preferably service account, you wish to connect to Allstacks.
Ensure appropriate Jira permission scopes for the project(s) targeted for the trial: Browse project, Assign Issues, Create Issues.
Login to Allstacks, select Add Tools
Assuming you are signed in to the Jira service account, when selecting “Get your API Token here” will open up a new tab. Create API Token in Jira, name it Allstacks, and paste it here.
Verify the Atlassian site name and email address
Click Add Tool button to connect.
On successful connection, you will see a list of resources you can toggle on and off that are repositories and projects, respectively. In the event this list is blank you may need to press “Refresh Resources”.
Jira (OAuth)
Alternatively, you may connect to Jira using OAuth service connection.
You can find your site name by looking at the url for Jira e.g https://{SITE NAME}.atlassian.net/
Jira OAuth integration must be performed by a JIRA site admin. It requires a few additional steps compared to a typical OAuth service. You will need to create an custom application link for Jira.