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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,529
Community Members
 
Community Events
176
Community Groups

Planning and Forecasting in Jira: Part 5

Let’s set up an example Jira project, and add some sample issues, so we can see the roadmap in action.

Jira Scenario

For this scenario create a software project called “Company Rebrand” to store all the tasks for a organization’s rebrand project. Follow the steps in upcoming sections to build the scenario in your test application.

Creating Projects

jira-projects.png

If you’re a Jira administrator, create the project in your test application by clicking the “Create” button at the top right of the page. Give the project a unique name (ex: Company Rebrand) and a unique key (ex: REBRAND).

Jira Project Templates

jira-project-templates.png

There are several software development project templates to choose from. I like the bug tracking template simply because its workflow includes a testing step.

If you don’t have Jira admin permissions or don’t want to create a new project, see if there’s a test project that already exists in your application. You can use it or any other existing project to try out this use case.

Now that there’s a Jira project, we need to create some sample issues to plan and track. First, think of all the work required when a company changes its logo and colors. Before creating issues, make a list of all the potential items.

Tip: I recommend building any Jira scenario on paper first. When all the details are worked out, then start creating and modifying configurations.

Here are the steps. Each shows an image of a hierarchical diagram. The diagram evolves as steps are completed.

Step 1

Instructions: Update Web Materials - we’ll need to update the entire website. That sounds like a lot of work, so let’s break it down into more manageable chunks.

diagram1.JPG

Step 2

Instructions: We’ll update all the logo files, the site styles, and make some changes on individual web pages. Let’s break these medium-sized items down, once more, into even smaller pieces.

diagram2.JPG

Step 3

Instructions: We’ll update the main logo files, the little icon that appears on a browser tab, and other co-branded logos.

diagram3.JPG

Guess what? This little listing exercise just determined our issue hierarchy in Jira!

The large body of work is the epic, the medium items are the tasks, and the small items are the sub- tasks.

diagram4.JPG

Step 4

Instructions: Let’s create one more epic and set of tasks and sub-tasks. Now we have a list of all the materials we’ll need to provide.

diagram5.JPG

Part 6: Jira Issue Structure and Importing

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events