How to Create summary report on # of linked ticket?

Question

So i have a 3 level hierarchy in my development environment, where there is an external project call CLIENT, which then get a clone internally for the developer to work on, lets call it DEV.  Those 2 tickets have ticket type as "bug" For testers, we want them to create a ticket type call "testing" and then linked to that bug internal ticket.

Since we know testers will be creating a lot of testing ticket, our management want to create some sort of report where tehy can see CLIENT-123 has 56 testing ticket, as well as internal development team lead to see that DEV-123 (bug ticket) has 40 out of 56 Testing tickets linked.

I know there is a link plugin out there, but thats not the report I am looking for.  If I need to a whole new reporting report, I am fine with that, but I just dont know where to start - liek should i do a gadget or reporting plugin...or something taht just do SQL statement?

Thanks in advance!

Eva8 · Answer

Hi Matt, thanks for fast reply.  Yes its only one JIRA instance.

I believe the reason we didnt use the issue security level is because we only want to show the client some detials but not all -- like subtask.  In addition, we dont want our users to create a ticket that meant to be private but somehow forget to set the issue security and thus showing up to our client.

So the way we have it structure is like this:

- CLIENT 1 created.  During a transition (where i have a postfunction plugin), it clone and craete an internal ticket DEV-1.  Right now I am still working on another plugin that moves the workflow in parallel...but as of now, DEV can have a different status than the CLIENT (unless someone move it, of course)

- Tester create DEV-2 (Testing ticket) and link it to DEV1.  Another tester create DEV-3 and do the same thing.

What I want to show is a list of CLIENT-XX tickets with # of Testing ticket, like this:

CLIENT-1:  3 < link would be nice but not require>

CLIENT-3: 15...etc

Thanks again for any help :)

MatthewC · Answer

I'm working on the assumption here that everything is in the one Jira instance but with different Jira projects? I'm also presuming that the split is because you don't want clients seeing internal chatter?

I would have thought that maybe using Issue Security Levels would be enough to seperate what a client can see from internal users based on project roles.

* Are issues linked at the top level CLIENT-1 linked internally DEV-1 ?
* Are CLIENT/DEV issues kept in sync during lifecycle?
* What goes back to the client & what do they see?

If you want, it's quite easy to write your own report in Jira which will be available from the Reports dropdown on the project page but that may assume that there is at least a link between individual issues so that it can follow the relationship