Better projektmanaging with better tracking and showings. But how?

[Thomas Bastian]

I like jira and the project issues. But as projectmanager, I have requirements for a professionell and modern management. 

f.e. I have this "normal" structure: Epics->requirements->working packages

It's no problem to structure alle issues in a list and sort for types or dates and so on.

But first, I need a real tree structure: per requirements, I want to see the linked issues. (I saw in my kanbanbaord-Backlog a tree structure for working packages under the requirements)

And I want to see all needed times (work, elapsed and so on ) in a view.

Is that possible without additional plugins? The plugin "Structure" is an ideal tool, I know.

bye, Thomas

[Bernhard Doleschel (Ease Solutions)]

Hello Thomas,

also a warm welcome to the community. You are right, Jira doesn´t offer nice option to structure the issues, especially when it comes to requirements management. 

Sorry, when I jump in here as a vendor. We have developed a add-on "R4J - Requirements Management for Jira" which allows you flexible structure your issues in a folder hierarchy. You can use you standard Jira issue types (or extend with customer and functional requirement types) to organize your project. We offer different views (tree view, reading view like a document, tabular view) to manage it, an coverage and traceability view to analyse you traces/links and export/import features.

If you are interested in a demo, please leave us a message in the service desk.

Best Regards

Bernhard, ease solutions

[Leo Diaz - Deiser]

Hi @Thomas Bastian !

It is very difficult (if not impossible) to have more sturdy projects in Jira without apps. My recommendation:

• Bigpicture or Structure: If you only want improve the issues strructure and have views to follow the structure:
  
• Profields: If you want to empower your jira projects and agregate into top level data or properties about your project:
  
  
  

[Thomas Bastian]

Yes, I know these plugins. But sorry, I need a solution without plugins.

but, thanks

[Jack Brickey]

Hi Thomas, welcome to the Community. Certainly Structure is well suited for this I expect. However, here is what I have done to manager traditional project management. I used Confluence to create traditional context about a feature/release, etc. I create a page and layout the goals and create a table for all requirements. The headers might look something like this:

Req#

summary

details

required/optional

phase

test case#

I fill in 2-5 as a Product Manager then I have the development manager create Jira issue in Column 1 and my QA manager (later) fill in column 6. Further, the QA manager would link the test case Jiras to the dev Jiras.

[Thomas Bastian]

Hi Jack, thanks for your welcome. 

that is traditional management, yes.  But my problem is in Jira and not confluence. Confluence is much more flexibel but have no issue database for statistics.

I need a solution in Jira as projectmanager.

[Jack Brickey]

So why can you not use Jira for your stats? What stats are you wanting to query? I use Confluence only as a means of getting started and setting context (words) for a given initiative. I can use Jira to determine the number of requirements done vs. not-Done fore example and similarly I can query stats on my testing. I can use Epics, labels and custom fields to break the larger initiative into phases, etc.

ultimately you will not achieve full Structure-like capabilities in standalone Jira but depended on your requirements you can often get close enough.