Skip to content

Commit 066e16a

Browse files
committed
Reordered sections
1 parent 15d4c47 commit 066e16a

1 file changed

Lines changed: 19 additions & 15 deletions

File tree

content/en/docs/developerportal/maia-plan.md

Lines changed: 19 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -134,18 +134,7 @@ After you click **Start Building**, the **Start Development** window is displaye
134134

135135
#### Connecting Maia Plan to Jira {#connect-jira}
136136

137-
Follow these steps to connect Maia Plan to Jira:
138-
139-
1. In the **Connect Planning Tool** window, select **Jira**.
140-
2. Fill in the information as follows:
141-
142-
* **Base URL Jira Environment** – The URL of your company’s environment within the Jira platform, as provided by Jira. This URL usually looks like this: https://my-company.atlassian.net.
143-
* **Project Key** – The unique key of your project within the Jira platform.
144-
* **Board ID** – The unique number which identifies a specific board in your Jira project/space.
145-
* **Jira Account** – The login name of a user on the Jira platform with project administration rights.
146-
* **API Token**: A valid API token issued by the Jira platform and assigned to the above mentioned admin user. For more information on how to get this API token, refer to [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
147-
148-
Make sure that the [prerequisites for using Jira](/developerportal/project-management/jira-connector/#prerequisites) are met.
137+
The following two sections describe the two main actions you need to take to use Jira as your project management tool in Maia Plan.
149138

150139
##### Configuring Jira for Maia Plan
151140

@@ -176,11 +165,26 @@ Existing Jira projects/spaces:
176165
* For a new board, select **All work items from your space**.
177166
{{% alert color="info" %}} When you select **All work items from your space**, a consolidated backlog view is created. This view includes work items from all boards in the project, not just those managed through Maia Plan. {{% /alert %}}
178167

179-
#### Using Jira with Maia Plan
168+
##### Configuring Maia Plan for Jira
169+
170+
Before you begin, make sure that the [prerequisites for using Jira](/developerportal/project-management/jira-connector/#prerequisites) are met.
171+
172+
Follow these steps to connect Maia Plan to Jira:
173+
174+
1. In the **Connect Planning Tool** window, select **Jira**.
175+
2. Fill in the information as follows:
176+
177+
* **Base URL Jira Environment** – The URL of your company’s environment within the Jira platform, as provided by Jira. This URL usually looks like this: https://my-company.atlassian.net.
178+
* **Project Key** – The unique key of your project/space within the Jira platform.
179+
* **Board ID** – The unique number that identifies a specific board in your Jira project/space.
180+
* **Jira Account** – The login name of a user on the Jira platform with project administration rights.
181+
* **API Token** – A valid API token issued by the Jira platform and assigned to the admin user mentioned above. For more information on how to get this API token, refer to [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
182+
183+
##### Using Jira with Maia Plan
180184

181-
Once you have connected Maia Plan to Jira, you can start using Jira as your project management tool, as follows:
185+
After you connect Maia Plan to Jira, you can use Jira as your project management tool:
182186

183187
1. In Maia Plan, in the **Start Development** window, set the planning tool to Jira, as previously indicated.
184188
2. Open the Jira board from Maia Plan. Your epics and stories are displayed in the Jira backlog.
185-
3. Create an active sprint in Jira, if one does not already exist.
189+
3. If an active sprint does not already exist, create one in Jira.
186190
4. Move the stories you want to work on from the backlog into the active sprint. The stories in the active sprint are now also available in Studio Pro.

0 commit comments

Comments
 (0)