Skip to content

AIO Tests

Report/overview of multiple projects

M

m999tvt

56 views

Hi,

There is a AIO library for each JIRA Project.

But we have acceptance testers working for multiple projects,

and they would like a visualisation on which project is expected from them over the multiple projects.

Instead of opening each project separately and go to the wished cycle.

Is there an advised way how to construct this overview?

What I had in mind now?

I suppose the precondition would be that the test cases should be assigned to this person.

And then the best is working would be using a dashboard.

Each acceptance tester should create its own dashboard - as they have other projects to follow.

That dashboard contains a gadget for each project they are working on.

(eg. gadget Execution Distribution- distributed by User Assignment, and only show the cycle execution)

All assigned users are shown, but that doesn't bother me. The specific user can see his/her name is there and find the needed info.

But ... that would be heavy maintenance each release. As each release they have to update each gadget with the new cycle selection.

Unless we work with a more general filter 'closed=no', so they only see the active/future cycles.

Then we have to make sure the team use the 'close cycle' once a test phase is done.

Or is there another approach? Looking forward to hear the ideas.

Thanks

Replies

2
Join to participate

Start threads and reply to conversations.

M

m999tvt

Permalink

Hi,

Thanks for the response.

That would be indeed nice - you may add it to the backlog,

as then we would not need to select cycle by cycle and maintain a lot via the reports/dashboards.

Image uploaded with this post

Only some thoughts when continuing on the current implementation:

(1) in my work, you see the cycles where you recently worked on.

  • As coordinator, I do a lot of administration. I see all the cycles I touched. Even those I don't have to actual work on. (no assignment of cycle nor test cases to me)
  • On the other hands, if the acceptance tester didn't open the cycle yet (95% of the time) .. the cycle would not be visible yet in the overview?
  • So he wouldn't be able to use this overview as actual place of truth. He wouldn't be aware cases are waiting for execution.

In brainstorm style, selection cycles would be something like

"non closed/archived cycles,

and where assignee of the cycle is the current user,

or where test cases are assigned to current user."

(2) And in extra should be available, as project icon / name of the folder where it's saved. So have more information/context of the shown cycle.

To be sure, I'm talking about my case and what would help in our organisation.

Thanks for your proposal,

Kindest regards,

Tamira

N

Niharika

Permalink

The My Work section on the Overview page today shows the cases assigned to a user across Cycles. However, this view is project wise. For the usecase presented, a gadget can maybe serve the purpose which exposes the My Work section in the Dashboard. If this works for you, then we can add it to the AIO Tests backlog.

Regards,

N

Browse all replies