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
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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs