nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Project Structure

Tony Skutnik

Sorry to ask. new Jira user here....

Simple project structure and want to set this up quickly. (Added a Microsoft analogy)

1) Releasing Software "Alpha" (Release MS Office 10)

2) Releases for #1 will be in 5 phases over time, each with a release date (Demo v1, Demo v2, Beta v1, Beta v2, Production)

3) Within each Phase in #2 will be 4 - 5 specific types of major technical functionality that are logical groupings (Excel, Word, Powerpoint, Outlook)

4) Within each type of major functionality in #3 there are tasks (Within Excel there are... a) Write specs b) development c) Testing

Question is - how do I organize? I tried the following but the Verison/Epic links are not cooperating. Per the above logic I setup:

1) Project

2) Version

3) Epic

4) Tasks

Our approach is each "version" (if that is the right term) is a major milestone. If I could associate multiple Epics with a Version it would seem logical, but I'm having trouble making that work in Jira. Maybe its me.

Before I debug, am I approaching this correctly?

BTW - I don't want to take up much of your time - so all I really need I the best practice groupings for steps 1 - 4 as noted above. I'll do the needed research.

Very small development team for now, so we don't need to make this complicated.

Thanks for the help

Accepted answers

All comments

Moses Thomas_08kyb0

@Tony SkutnikIt is easy to associate Epics with versions, simply add version to project, we have two system fields for versions(fixed version/s and affects version/s) you just need to create screens and add any of these fields to screen and associate screen to issue type (Epic, Bug)

You can also set field to required if needed by create separate field configuration for these issue type.

Best!

Tony Skutnik

Thanks - Since our Epics are within Versions, can I just associate the task to the Epic and the Epic to the version? When I tired it I had to associate each task to both the Epic and the Version, and that's an extra admin step for all of our tasks.

Also - do I have the right structure (1-4 described above) for what I'm trying to do, or is there a better way?

Tony Skutnik

Also - do I have the right structure (1-4 described above) for what I'm trying to do, or is there a better way?

Moses Thomas_08kyb0

@Tony SkutnikYes you can once you create an issue of type Epic, view this thicket you will see issues in Epic click the + sign to create issue of type Task and choose Fix version/s on the screen once created you have successfully associate task with both Epic and version

Best!

Moses Thomas_08kyb0

@Tony SkutnikIn-fact this is the approach you should use

Tony Skutnik

Thanks for the response - but let me make sure I get it. When I create a task I need to assign it to BOTH the Epic and the Version. I'm trying to assign the Tasks to the Epic and the Epic (not the tasks)to the Version, hoping that any tasks I associate to the Epic are automatically associate with the Version. Is this possible or do I have to assign tasks to BOTH the Epic and the Version.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud