Jira version hierarchy

By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. Project Management Stack Exchange is a question and answer site for project managers. It only takes a minute to sign up. To accomplish this, define your Epics and give them each an "Epic Name". Then define your Stories, and within each one select the appropriate Epic within "Epic Link".

From each Story, as needed, create any Sub-Tasks. To give an example, if I were defining all this for, say, the workflow module of an application, I might end up with something like:. Jira does a good job at abstracting a lot of this, but it's not geared toward your exact approach, and trying to get it to visualize things the way you want rather than the way it wants is often an exercise in futility.

In JIRA, there's only really support for two levels of issue hierarchy--task and subtask. An Epic is unique and behaves more like an attribute of another issue. Kind of like how versions are just attributes that help with structuring the work in your project. In textbook scrum, the only hierarchy is stories and the subtasks that get them done there's no such thing as a 'Feature', so to speak. When a story is too big to fit into a single sprint, it's split into smaller stories, and the original 'big story' becomes an Epic and is used like a label to indicate the smaller stories have a common origin.

But it's not unusual to step outside of textbook scrum, and a lot of people use Epic like another dimension of Components or requirement categories. It's just that, as far as how JIRA is designed, other approaches have to be shoehorned into this textbook model.

I recommend evaluating Structurean add-on that lets you define custom issue hierarchies.

jira version hierarchy

It's one of those add-ons where you keep finding more ways it can help you work, too. I can't think of any other way to help you. Sign up to join this community. The best answers are voted up and rise to the top. Home Questions Tags Users Unanswered. Asked 5 years, 1 month ago. Active 4 years, 3 months ago. Viewed 16k times. How can I setup this hierarchy in Jira? Marv Mills 4, 1 1 gold badge 15 15 silver badges 27 27 bronze badges. Phill Pafford Phill Pafford 1 1 gold badge 1 1 silver badge 3 3 bronze badges.

Looks like Wandering NPC is on the right track. See the discussion thread on Atlassian Answers here.Join the community to find out what other Atlassian users are discussing, debating and creating.

With Structure plugin, I linked Epic Feature and Story but the problem is when I update story tickets there's no progress in Epic in the Agile Backlog Board, epic progress gets updated only when the feature is updated there's no relation between stories and epics now.

You can actually change the name of the Field that will work as an Epic on Agile boards to anything you want, including Feature. As for rollin-up progress, you should be able to see it in Structure. If something doesn't work, please let us know and we'll be happy to look into it. You can leave a comment here or open a ticket in our JIRA:. You must be a registered user to add a comment.

If you've already registered, sign in. Otherwise, register and sign in. I was curious if you ended up just using Portfolio and changed the name of Epic to achieve your desired hierarchy? Or if you ended up using Structure. I was about to do a similar test using Portfolio and was just curious of your outcome. Hi Eugine, Link for changing epic description no longer works. I get message Unavailable item. I'm not sure what could be the case there. Maybe something was changed in the later versions of Jira.

I haven't tried it myself yet, but it seems like a good far more complete solution for this scenario - it even translates the link type name and works for JQL queries too. So how do you view details for tracking purposes. This is all out of the box functionality in Team Foundation Server. That's a pretty myopic view. Adding additional layers isn't very "Agile", and Jira is built around those best practices.

This hierarchy is entirely possible and not difficult, but why create the additional overhead? I would rather use flexible tools which allow teams to start where they are, and gradually improve. Absolutely agree. An additional layer of focus is very valuable I just keep getting some raw wood and am told to get a saw and start building because Jira is so flexible and customizable. What makes me so frustrated about using Jira compelled to do so at the moment is I don't get paid to build tools, I get paid to create commercial features.

This is not a hobby for me it is a job and I get measured by output not cool things that don't create revenue. Creating those scale tools is Jira's job. Unfortunately, management is convinced that Jira does everything necessary Btw, plugins are too costly to go for I am also looking for a view showing this simple hierarchy since my pieces of work are that big and need the break down to be small enough in a sprint.

How can you make that visisble in Structure or Portfolio? I can be reached at vlad almworks. I want to be able to drill down in the tree structure down to task in one view so I quickly can overview what is planned and refined.

There are a couple different ways to achieve this. For instance, you could start by Inserting your Epics into the structure:.Join the community to find out what other Atlassian users are discussing, debating and creating. I thought the relationship would be that Stories are assigned to Epics, and Epics are assigned to Versions.

It seemed a good way to keep track without just throwing a ton of Stories into a Version. I don't see a way to associate Epics with Versions.

Subscribe to RSS

They just stay in their column. I can drag and drop Stories onto Versions How does that make sense? What good is the Epic if you can't use it to organize Stories in the Agile Board view? To associate an Epic with a version, it's true that you can't drag and drop it in the Version tab, but that's just one of the ways of assigning a version.

If you make sure that in the Screen Scheme used by Epics, the Affects Version field is present for the Edit operation, you can just edit the Epic and select a value from the available versions. Ideally, to do this in as few steps as possible, you should select a version at the creation of the Epic, again, provided your Screen Scheme displays this field on Create.

You can also do a Bulk Change if you're in the Issues view to quickly set several Epics to a given version. You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in. This still doesn't cause associated epics to be "not-opaque" when you have the associated release highlighted Maybe I'm still missing something though.

I have the epic set in Affected Version s and Fix Version and it still does not sort my epics based on my version selected on the left column of the plan view. It is not working for me too.

jira version hierarchy

I tried to write the version name on affected and fixed version fields and I could not see any link between epics and versions. Did you ever find a solution to this? I'm assuming that your end goal was to visually separate the EPICs and its User Stories within the project into two or more distinctive Version so you could better manage the project? We've been stripping down processes a bit to make the next-gen stuff work for us.

It's mostly helpful.Versions are points-in-time for a project. They help you schedule and organize your releases. Once a version is created and issues are assigned to it, you can use the version to filter information in various reports. If you've integrated Jira with Bamboo, you can start a build automatically.

For all of the following procedures, you must be logged in to Jira as a project administrator. Go to your project and click Project settings. The Versions or Releases page is displayed, showing a list of versions and each version's status. From here you can manage the project's versions as described on this page. Versions that include end dates can indicate when a release is overdue.

jira version hierarchy

The release date appears in red for unreleased versions that have passed their planned release date. The status affects where the version appears in drop-down lists for version-related issue fields, for example Fix version. On the Releases or Versions screen, select Create version.

Give the version a name. You might organize versions by number, for example "3" or "3. Or you might use code names, for example "Corvette" or "DeLorean". If specified, the Start date is used by the Version Report. This gives you a more accurate report in cases where you might plan a version many weeks or even months in advance, but not actually commence work until closer to the release date. Marking a version as released will affect some changes in some reports and some issue fields' drop-downs.

If you have integrated Jira with Bambooyou can trigger a Bamboo build to run automatically when releasing a version in Jira. The version will only be released if the build is successful. For more information, see Running a Bamboo build when releasing a version. On the Releases or Versions screen, find the version you want to release.

To revert the release of a version, simply select Unrelease from the actions menu. On the Releases or Versions screen, find the version you want to archive. To revert the release of a version, simply select Unarchive from the actions menu. On the Releases or Versions screen, find the version you want to merge into another. On the Releases or Versions screen, find the version you want to edit. From here, you can specify the actions to be taken for issues associated with the version.

You can either move these issues to another version, or simply remove references to the version you want to delete. Rescheduling a version changes its place in the order of versions.

On the Releases or Versions screen, drag and drop versions into the release order you prefer.Structure for Jira helps Atlassian's largest customers visualize, track and manage progress across Jira projects and teams. It does this with adaptable, user-defined, issue hierarchies presented in a familiar spreadsheet-like view of Jira issues.

For us, Structure is essential for organizing these issues in a way that allows us to manage them effectively and get the job done. Issue hierarchy may have any depth sub-issues, sub-sub-issues and so onand contain issues from multiple projects and of any issue type. A structure may include important tasks and milestones from all projects in the company, and provide overview of the progress for the management — in Jira or in an Excel report.

Whether it's a new employee checklist or a test plan, you can save time and effort by cloning a pre-populated template structure instead of creating all the issues by hand. When issues are collected into meaningful structures, you can quickly browse them and see the context of each issue.

jira version hierarchy

Track total time spent, total estimation or overall progress — Structure aggregates this information upwards through the hierarchy. Get a single view of an already existing hierarchical relationships, represented as issue links, sub-tasks or Agile Epic-Story links. Structure has a well-documented API, allowing integration with your existing infrastructure through additional custom-made Jira add-ons. Extensions like Structure. Testy and Structure.

Pages are an example of what can be achieved with the API. Gantt Add the power of Gantt charts to Jira projects Structure. Gantt Overview Atlassian Marketplace.

Pages Overview Atlassian Marketplace. Testy Test checklists extension for Structure Structure. Testy Overview Atlassian Marketplace. Colors for Jira. JQL-based color highlighting for enhanced issue navigation. Client for Jira. Interactive desktop client for Jira. Saves you several seconds of your time, per issue, per day. Works offline. Structure Version: 6. Gantt Version: 2. Pages Version: 1. Testy Version: 2. Version: 2. Version: 3. Colors for Jira Choose your platform: Server Pricing.

Client for Jira Choose your platform: Server Pricing. Pages Support Request Documentation. Testy Support Request Documentation.Ask the community.

You could map Jira Software stories, bugs, and tasks into custom Portfolio for Jira levels. Keep in mind that this configuration will be applied to all plans.

Before mapping a Jira issue type into Portfolio, make sure that the issue type has been created in your Jira application instance. Once you've created your new issue type in your Jira application, it's time to map it into Portfolio.

Note: The Epic issue type is tied to the Epic hierarchy level in Portfolio for Jira, and can't be changed. You can create as many hierarchy levels as you want in Portfolio for Jira by following these steps:. Unable to load. Cloud Server Versions 3. Configuring initiatives and other hierarchy levels How to create a new hierarchy level in Portfolio for Jira How to add a new initiative level to a Jira project Exposing the hierarchy configuration in Jira Software.

It's not the same without you

Related content No related content found. Still need help? The Atlassian Community is here for you. Before you begin Before mapping a Jira issue type into Portfolio, make sure that the issue type has been created in your Jira application instance. Tip Remember that you can add hierarchy levels above the epic level only. Was this helpful? Yes No It wasn't accurate. It wasn't clear. It wasn't relevant. Powered by Confluence and Scroll Viewport.Out of the box, Jira Software has many features that make it an ideal choice for task tracking and team management.

Jira provides workflows, custom fields, and issue types. Almost anything can be customized for the precise needs of your organization. However, the situation becomes more complicated when an organization has multiple teams working in concert on one or more large business initiatives.

Good project portfolio management PPM practices and tools are critical as the organization expands and it becomes harder for teams to remain aligned. At the same time, management wants to get a sense of the big picture. They want to be able to identify and understand where problems are arising in the process. There are several solutions on the Atlassian Marketplace that can help with this challenge.

One of the key features of Structure for Jira is the ability to arrange Jira issues in unlimited hierarchies. Structures can represent Jira project information in many ways. You can use them to visualize the relationships that exist in Jira, such as Issue Links, Epic Links and sub-tasks. This makes Structure quite a flexible tool that allows teams to use hierarchies for all kinds of purposes. With Automation you can add issues from Agile boards or by using JQL, visualize relationships that exist between issues, or filter, sort and group by any field you like.

To build your structure, you add Generators. Generators are special rules that define how your structure should be built.

The Complete Structure For Jira Guide: How to Structure Your Issues Like a Pro

By using generators in different combinations you can deliver powerful results. They enable you to quickly assemble and present the information that matters most. The issues in your structures are shown as rows and the information about the issues — in columns.

To see this in action you can watch ALM Works webinar on live tracking and reporting here. Views can then be shared with other users, associated with particular structures, or set as defaults.


Comments on “Jira version hierarchy