Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Jira and Jira Align Integration Glossary

API Token: API Tokens can be used for authentication between Jira Align and Jira Cloud.  You can use an API token to authenticate a script or other process with an Atlassian cloud product. You generate the token from your Atlassian account, then copy and paste it to the script.  More can be read on API Tokens here:

Agile Team: An Agile team is related to one program, and members of the team can access all the team’s data and have some visibility into other teams in the same program.  A Jira Align Agile Team typically corresponds to a single Board in Jira.  More can be read about Agile Teams here:

Anchor Date (Sync Sprint): In Jira Align, a program increment has a series of dates called synchronized dates or anchor sprints. These dates are used to provide milestones for coordinating across teams, for example, for negotiating a dependency.  The end date of a Sprint from Jira will map to the end date of a Jira Align Anchor Date to map sprints from Jira to Jira Align.  More can be read about Anchor Dates here:

Buffer Days: When the first active Jira sprint is brought into Jira Align, the end date is recorded in Jira Align. It is matched to a Sync Sprint within the buffer date range set under Administration > Connectors > Jira Settings > Jira Setup > Sprint Buffer Days (generally 3-5 days). All future sprints on the Jira board are then matched in board order to the next in line Jira Align Sync Sprint.  More can be read on Buffer Days here:

Capability (Sub-Initiative): Capabilities are similar to features, but they describe higher-level solution behaviors than the features do. Capabilities fit within a single release to assure that each release delivers incremental and measurable value. They are also used by large organizations that break down epics to a more granular level.  Capabilities will live in Jira Align, not sync between Jira and Jira Align, and will be the Parent work item to Jira Align Features.  More can be read on Capabilities here:

Defect (Jira Bug): A defect is a condition in software which does not meet a software requirement or user expectations. Defects are used to identify differences between what is expected and what is actually produced. In Jira Align, defects are created and managed in the Defects module using the Defects Grid.  Jira Align Defects will sync with Jira Bugs by default but can also be configured to sync as Jira Align Stories as Type Defects.  More can be read on Defects here:

Epic (Initiative): Epics are large, typically crosscutting, customer-facing initiatives that include new development necessary to realize certain business benefits. Multiple capabilities are typically assigned to an epic, and an epic may span multiple releases. Multiple features can be tied to an epic if this epic does not have any capabilities.  Epics will live in Jira Align and will not sync to Jira.  More can be read on Epics here:

Feature (Jira Epic): Features group user stories and represent functionality customers will use. Multiple stories are typically assigned to a feature, and a feature fits within a single PI.  Features in Jira Align will sync with Jira Epics in Jira.  More can be read about Features here:

Filter Share: A Jira filter whose creator has shared that filter with other users.  The Filter Share can be found on a Jira Board's Settings on Configuration. You can share a filter with a Project—All members or members with specific project roles working on one or multiple projects, Group—A group of Jira users, Open—Any user who is logged-in to your Jira Cloud site, Public—Public sharing means sharing the dashboard with users who are not logged in to your Jira Cloud site. Note that if you share a filter publicly, it will be visible and searchable on the internet. See Prevent or remove public access for more information, and Private—Only you can view the filter.  Jira Board Filter Shares will need to be set to a Project in order to properly map Teams between Jira and Jira Align.  More can be read on setting a Filter share in Jira here: More can be read on why the Filter Share should be set to a Project here:

OAuth:  OAuth is one of a number of authentication methods that can be used between Jira and Jira Align; and is typically used for server-to-server authentication, especially for behind the firewall applications.  More can be read about OAuth here:

Origin Board ID: The Origin Board ID is the ID of the Board in Jira where a sprint was created.  When "only sprints created on board" is enabled in Jira Align the connector will only map sprints where the Origin Board ID matches the integrated Board's ID and "sprints created and shared to board" is enabled the connector will map all sprints shared with an integrated Jira Board.  More can be read about the Origin Board ID here:

Planning (Bucket) Sprint: A Planning sprint is a sprint created in the Jira Backlog outside of a published Scrum Cadence that teams utilize to plan future work.  Jira Align predicts the start and end date of future sprints as sync from Jira, so a Planning Sprint in the Jira Backlog would lead to sprint alignment errors between Jira and Jira Align.  More can be read on planning sprints here:

Program: A program, also called a release train in the Scaled Agile Framework, includes a set of product management and development teams that work from a shared backlog and coordinate team of teams meetings. Teams within a program usually only work on products and projects for their own program, though occasionally might coordinate work with other programs.  Jira Projects will be mapped to a Jira Align Program.  More can be read about Programs here:

Release Vehicle (Jira Fix Version): A release vehicle represents an actual release to market or to internal end users of software.  Jira Fix Versions and Jira Align Release Vehicles will sync Bidirectional.  More can be read about Release Vehicles here: More can be read about syncing Release Vehicles and Fix Versions between Jira and Jira Align here:

Sprint (Iteration): A sprint is an incremental delivery cycle, usually spanning from one to four weeks. Every sprint starts with a sprint planning meeting. At the end of the sprint, there is a sprint review meeting, followed by a sprint retrospective meeting. The end date of Jira Sprints will map to the end date of Jira Align Anchor Dates which will create corresponding Team Sprints in Jira Align.  More can be read about Sprints here:

Task (Jira Sub-Task): Teams perform tasks to deliver a backlog item. Tasks are all the work the team must complete to accept the story as done.  Tasks in Jira Align will sync with Sub-Tasks in Jira.  More can be read about Tasks here:



This is extremely helpful! Thanks Tim!

Super helpful!. Thank Tim!

Like Tim Keyes likes this
Michal Szymandera
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 11, 2020

Thank you Tim :-)

Like Tim Keyes likes this

Nicely explained and good information. Thanks Tim.


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events