JIRA Usage- ASAP discussion

[Shira Izon]

Hey all,

I would like to hear your opinions regarding JIRA implementation in my office-

in order to clarify the right usages of that system.

If they develop a generic platform of Features but they have wanting to Choose whom system these features will be adjusted/implemented.

How to define the Features list in JIRA? 

How can you express/reflect -the features classification per system ?

Thanks! 

[Nic Brough -Adaptavist-]

Use an issue type called "feature" and a field to select the system from.

You'll then be able to run reports and searches based on "issue type = feature and system in (x, y, z)"

[Shira Izon]

ok,.  but Issues Types are divided just to EPIC / STORY/ BUG / TASK ? Is there an option to rename it ?

[Nic Brough -Adaptavist-]

No, you can add more issue types, and rename any you want (just do NOT rename Epic, it breaks some stuff if you do that, although Atlassian are working on getting rid of that problem)

[Shira Izon]

Can you show me shortly  (guide) how to add issues types? And I hope you understand my question so that the features  classification to systems can be by different projects?

Thanks a lot!

[Nic Brough -Adaptavist-]

See https://confluence.atlassian.com/adminjiracloud/adding-editing-and-deleting-an-issue-type-844500747.html

Saying "features classification to systems" is very vague, all it tells me is that you want to have some way to distinguish issues from each other.  You can do this with fields.

[Shira Izon]

In this way (adding issue type called "Feature") -You need first of all choose the project and then can see ALL the related features.

But the filter from the other side is available ? To link a feature for several projects /systems.,

This our need from JIRA

[Nic Brough -Adaptavist-]

I am sorry, I do not understand most of that.

If you add the issue type "feature" to Jira, you can then enable it in any project you need it in, by adding it to the issue type scheme for the project.

I have no idea what you mean by "filter from the other side"

[Shira Izon]

Our goal is to develop a generic platform of features and to link them in part of the projects. 

Is there an option to filter all  features list and to see which projects they are linked to?

Indeed what you suggested is to define feature (as issue type)  but I need to link it again and again for each project ... 

Thanks!

[Nic Brough -Adaptavist-]

>Our goal is to develop a generic platform of features and to link them in part of the projects. 

Ok, but again, I do not understand what "part of the project" might be.

>Is there an option to filter all  features list and to see which projects they are linked to?

Yes, search for "issuetype = feature" and the list of feature keys will give you the projects they are in.  Or you could add the project field to the display.  Or if you are thinking about issue links, add the link field to the display.

>Indeed what you suggested is to define feature (as issue type)  but I need to link it again and again for each project ... 

Again, I don't get what that means.  To "link" features again and again, add issues to the project to represent them.

[Shira Izon]

Hi again.

I've tried to define a new issue type called FEATURE (let's name it A), but this A should be existed in several projects = systems.

1. Now, I need to enter (separately) in all those projects and create this A issue type ?

2. What is happen if I have a list of FEATURES?

3. How can I introduce/filter  these created features into the board. in order to see which features related to which projects? (configuration fields idea is failed)

4. As I know the steps, you need first of all choose  a Project Name and just after that you choose the Issue Type value. 

So that the way to create any issue type for multiple projects is Sisyphean (non effective)?! 

It seems like a last trial to use / recommend JIRA system for that Business goal

Thank a lot and all the efforts to assist me - appreciated :)

Shira

[Nic Brough -Adaptavist-]

1.  If you are using classic projects, then possibly.  You will need to add the new type to the "issue type scheme" for each project, but the issue type scheme can be (and is intended to be) reused - if your projects are all using the same scheme, you will only need to add it once

For Next-gen projects - yes, you will need to add it to each project

2.  I do not think the question is clear.  If you have a list of features, then you have a list of features, there's nothing more than that, nothing "happens" just because you have a list

3. Most filters (and hence boards) will include them automatically when they match the query behind them.  Only filters that exclude them will need to be altered

If, for example, a filter includes "and issuetype in (bug, story, issue)", then it won't be selecting for them.  If a filter does not exclude them, (for example a very common filter is "Project = X"), then they will be included as long as they match the rest of the clauses in the filter

To see what features are associated with a project, look at the key of the feature, it contains the project key.  To get a list, try a search for "issuetype = feature and project = 'my project(s)'