How to add deferent verticals in jira?

[Vishnu Vardhan Chenna]

Hi 

we have deferent types of verticals like 

Business Vertical

IT Vertical

SAP vertical

DE vertical

each verticals has Divisions and Sub divisions 

How to ensure this structure in Jira software?

[Walter Buggenhout]

Hi @Vishnu Vardhan Chenna

Modern organizations are almost always using some kind of matrix structure to organise themselves. This usually reflects in the way teams are formed across departments and parts of the org chart. It is usually no longer possible to poor this into a fixed hierarchy anymore.

So a common approach is to set up custom fields that hold the specific entries for each of those verticals you mention and add select the appropriate values on the issues in Jira using those custom fields. That will allow you to filter the issues by each of those verticals, regardless of any other hierarchy you have in place inside your org chart or other organisational structure. In practice, they become more like tags or metadata that help you organise/categorise the work.

Hope this helps!

[Vishnu Vardhan Chenna]

Hi @Walter Buggenhout 

Thanks for the suggestive approach. This approach is known to us. Although, we are looking for setting up the custom fields in the project details level not issue level.

Consider an example of getting all the projects from JIRA run by one of the CoEs in an organization. There might be 100s of projects running in this CoE, we may not want to go to issues in each project to get the projects list. We should be able to get the list by a field from the project details itself.

Hope you understand our issue.!

[Walter Buggenhout]

Hi @Vishnu Vardhan Chenna,

I think I do. At project level, there is not much you can do out of the box. The Project Category is indeed one you can use to associate projects with a department. But you can only add one for each project, so choose wisely (and consistently). Big benefit is that you can easily create filters based on that field to build a dynamic backlog.

If you need to store more details at project level, you may need to look into the marketplace for a tool like e.g. Projectrac. That is designed to enrich your project level details.  

[John Koenig]

We have the same issue as mentioned above. We need like an organization level where projects and below can be added. Has this issue or problem been addressed? 

[Sachin Dhamale]

Hi @Vishnu Vardhan Chenna .

Can you provide the more information about your process? What is the verticals/division/sub division  defines.

In Jira We have this Structure

Project > Issues 

For Project - We have Project Category ( this is some like property) - based on that you can bifurcate project

For Issues - here we have this hierarchy  Epic > Story/Bug/Feature (Standard Issue Type) > Subtask  this is basic hierarchy jira provide. 

In Jira we also has Issue linking - Based on that you can have linking between issues. 

Like I mentioned its based on your process. you can configure and accommodate it in jira structure.

If your case I am assuming vertices are nothing but different department. you can managed them as a groups a groups or project roles.

and apply them to the respective projects as per their permissions.

Thanks,

Sachin

[Vishnu Vardhan Chenna]

Hi @Sachin Dhamale 

you mentioned that issue linking- but issue linking feature is not working in jira cloud could you please help me in this case

[Sachin Dhamale]

Its there in Jira Cloud. It might be deactivated for your site. 

Go to the Issue Linking Setting from admin section if you have jira admin rights. 

Simply add this to your site URL - /secure/admin/ViewLinkTypes!default.jspa

[Vishnu Vardhan Chenna]

@Sachin Dhamale 

issue linking option is there and it is in active state.

when I have created two issues X and Y

X linked with Y and X blocks the Y. if X issue completed then Y issue should be starts.

but here it would not happened. I can completed the Y issue before X issue is not complete.

[Sachin Dhamale]

@Vishnu Vardhan Chenna 

In Jira Issue linking is just used for showing relationship between 2 issues. 

There is no any restriction you impose using linking. You can use  automation rule where based on linking you can move the link issue to Done as per the status of other link issue

If you want to impose such restriction then you need to use third party plugins like JWMC, Scrip Runner plugin