overview for request that need tasks in multiple projects

[Anca Cristescu]

Hi,

I want to create a report/view/something to show the lifecycle of a request that starts from a PM task, goes to a product analysis , then development does the 'needful' and then tech team gets the build to the customer ...

So I have 4 projects, with 4 tickets linked together, but I don't know how I can see  this in a nice view ... 

* time in each status (in each project)

* owners

* logged time

*...

Can anyone give me some hints on how to achieve this in Data Center? (preferably :) )

Thank you,

Anca

[Danut M _StonikByte_ · Accepted solution]

Hi @Anca Cristescu,

If you consider a solution based on a plugin, I think you can get such view by using the Pivot Table & Pivot Chart gadget offered by our Great Gadgets app.

Here is how:

• Have a field of type Label that represents the request. Possible values could be Request-A, Request-A, etc... 
• Set this field to all 4 tasks of the request. So all the 4 tasks related to request X should have this label field set to Request-X. This way you link the 4 tasks related to request X together.
• Configure the Pivot Table & Pivot Chart gadget like this:

Data tab

More settings tab:

• As a result, you will get a view like this:

My example does not display the time in status. But if you would add an automatically calculated field like "Age" which is the time since issue creation, you could add this to the pivot table. I think such field can be added with Script Runner. Or, you could use the Time in Status gadget that our app also offers. 

Hope this helps.

Danut.

[Anca Cristescu]

Thank you @Danut M _StonikByte_ :-)

I have tried both gadgets and Time in Status is the one that gives me a very nice overview on ALL tickets I need.

I did not consider initially the pivot table (my mind is not set to think in pivots :D), but I like this view also, for a very exact view on all tickets in the flow .

Now I need to make sure the users follow the procedures, so all tickets have the connection field. (spoiler alert... they will not)

[Danut M _StonikByte_]

Hi @Anca Cristescu,

I think you can solve this problem by making that field mandatory (by marking it required in the field settings/schemes) for the issue types that will contain it. 

Danut

[Alexander Hohmann · Accepted solution]

How about creating a hidden custom field whose content is automatically copied into a similar hidden field in the work item of the next type, who then appends further elements to it on the go, and then copies it into the next work item, and so on? At some point (or for some users), the field could be made visible.

[Anca Cristescu]

Thank you @Alexander Hohmann

A common (hidden) field is a good option to connect all tickets.

[Dmitry Astapkovich _Colined_]

Hi @Anca Cristescu ,

With Pivot Report we develop you can get a view like this:

Time in every status can be added as separate columns. 

You can check this demo report on your own, no login needed.

[Ravi Sagar _Sparxsys_]

Hi @Anca Cristescu 

If you are on DC then you can create a plan across multiple projects. Not sure if you have any hierarchy but you can have some levels above your Epics. Something like Initiatives > Epic > Story > Sub-tasks

Project 1 can just be for Initiatives.

Other projects can have Epics and stories.

You can create a plan to visualise all of this under one view.

[Anca Cristescu]

Hi @Ravi Sagar _Sparxsys_ ,

We already have a hierarchy set in place that is not compatible with 'my dream' :). It is defined only to accommodate development projects, not PM, Product, tech.

Thank you for the idea. I'll test it and see if I can start a revolution :).