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

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • 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

Using Components, Epics or Labels for client-projects?

We're a small web agency and are currently working with a project for each dept. -> DEV (Developer), MAR (Marketing), DES (Design),... . Since a lot of our client-projects are processed company-wide, we are using "Labels" with some quick filters for tagging each client. 

I suppose this is not the best method and probably some of you have faced the same problem. I discovered Components and Epics as a probably better solution for our case - what would you recommend or have you eventually a better solution?

Thank you very much! Greets, Martin

2 answers

0 votes

If you're all in one project, that would be a perfect use for components.

If you've got several projects, then it might be worth using a custom select field globally (or multi-select if there's cross over between clients)

Epics are not for tagging things, they're there to represent large chunks of work.  That could work very well if you use them for "client project", as they'll eventually be closed down.  But it won't work properly for just "client"

Hi Nic, thank you very much for your response!

So it would be a good way to -> tag clients with custom select field globally and use epics e.g. for bigger tasks like "Website project client XY" or "Marketing campaign client XY"? 

So we wouldn't using components although they come with some interesting features like the default assignee option. 

Thanks, Martin

Yes, that does sound like the best way to go to me! 

You could still use components for something else.

One other possibility to consider would be using Project Categories - one for each department, and then use Projects for each client.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

3,998 views 11 5
Join discussion

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