A simpler way for our team to view their work

[Andrew Stone]

Hi There, 

Our team is struggling to find a meaningful solution for a 'my work' section in JIRA. 

We have multiple projects that our team contribute to. Each staff are contributing to multiple projects and we're struggling to find a useful view to see a list of projects and the assigned tasks at a glance.

Please see how simple it is within ASANA

Basically a list view like this: 

Project

- Task

- Task 

- Task

[Nic Brough -Adaptavist-]

Another option is to create your own "my work" dashboards - there are all sorts of gadgets you can add and customise for them.

The most obvious one is a simple "filter list" - define a filter like "assignee = currentUser() and resolution is empty order by project", save it, and use it in a filter view gadget.

[Dave Liao]

@Andrew Stone - hi Andrew!

If you're managing smaller projects:

1. Consider organizing your project Tasks/Stories within Epics in a single Jira project.

For that Jira project, use a board and go to the Backlog view to visualize your work.

(This might not be practical for larger projects, however.)

2. Using Jira Work Management ? The List view might be useful.

For larger bodies of work, you may need to try a third-party app from the Marketplace to better visualize your team's work.

[Jimi Wikman]

A common situation for Kanban teams with multiple clients, like in BI or integration.

A common setup is to use Epics as "projects", or rather delivery packages. You use Components to map up your own structure, or the clients, depending on what works best for your setup.

Based on your screenshot, you are working with websites, so then each website would be an epic and each section would be a story/task that you then break down into subtasks (frontend, backend, configurations, graphics, texts, translations and so on).

This way you can also use the roadmap to do a rough time planning using a Gantt setup. I also would use the Scrum Board, so you can plan your time easier in either sprints or on a monthly/quarterly basis. This will also allow you to see if someone has more to do than they should have in that period.

You can set up the lanes to be based on epics and/or color the cards based on project or assignee to visualize better.

You can also set up issue types to better fit the work you do (design, frontend, translations, tasks, analytics, SEO....) to make it even easier to see what work is done and who is doing it. That way you can also ensure that the workflow for each activity match the work you do.

---

If you contribute in multiple Jira projects, then you can either create a Jira project and filter in all work from the different Jira projects into that project, or you can create a board on top of the projects.

You need a way to mark what items your team should have in their board from the different projects and if you make that generic you will not be able to use a Scrum board anymore as it require the query to have projects connected to each query.

[Dmitry Astapkovich _Colined_]

Well, that would potentially be a bit of an overkill, but this one of many use cases for Pivot Report that we develop: 

You can play with the demo report on your own. It has a lot more than just "Your work". And yes, filtering out only current user issues is easily doable.