Using Components, Epics or Labels for client-projects?

[Martin Tauber]

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

[Dave Collins]

https://moduscreate.com/blog/jira-using-epics-vs-components-vs-labels/

[Nic Brough -Adaptavist-]

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"

[Martin Tauber]

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

[Nic Brough -Adaptavist-]

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

You could still use components for something else.

[Chris Dunne]

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