Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What is the best way to run multiple projects (development + support)?

I usually have 2-3 software development projects and about 7-8 development support projects. I do not have separate teams, and, I see that multiple team members are aware of the code so that when a production issue occurs, individual with time can attend to it.

For these oddly 10 projects, and a single team, I've 10 boards.

  1. What is the best way to keep things organized so that no one misses any jira added?
  2. What is the best way for me to track these 10 boards in one go?
  3. What is the best way for the team members, every one of those, to track their tasks with priorities at a single place?

Links to relevant reading articles appreciated. *New to jira, sorry and thank you for answering such naïve questions.

1 answer

1 accepted

0 votes
Answer accepted

Hi @SHRIKANT SHET,

Welcome to Jira and welcome to the community

This is almost a consultancy question, to be honest. But nevertheless, let me give you a couple of pointers here:

  • Don't use 10 different boards to manage the work of a single team, but try to consolidate this into 1 or 2 (a board can get its data from a filter across multiple projects)
  • If you separate your work into 2 different boards, it would make sense to separate the development and support work. Development work is usually planned upfront, whereas support work flows in
  • Don't just look at the tool, but also (and maybe in the first place) at how you are organised. If you let your people work on support for a longer stretch of time and for another stretch on development, that would support my previous suggestion on splitting the work. If your team members mix support and development work all the time, having a single board may be better.
  • Use quick filters on the boards (they are available out of the box) to let people filter out their own assigned issues directly on the team board.
  • Considering setting up a personal dashboard, where people can see a.o. the open issues assigned to or reported by them and the issues they are watching across all Jira projects. Use assignee / reporter / watcher = CurrentUser() to make the filters generic.

And indeed, read, read, read the documentation on how to set things up!

Thank you Walter for the detailed explanation! Look forward to using the gem of advice!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you