Create epic on roadmap view with label

[David Heath]

I have a jira board which uses a label filter to control which epics and issues are shown on the board.

When I click "+ Create epic" on the bottom of the new Roadmap view, I get an alert saying that it's not visible due to the filter?

Is there a way to have the epics I create in this manner automatically get the right label applied?

[Chris Buzon]

It depends on your use case I think,

Creating the epic from that view doesn't do anything differently (that I know of) than creating it from the large create button at the top of JIRA - it just skips a couple of steps.  You can use the fact that it's creating Epics in a specific project for automation triggers, but whether this solution will work is going to be based on when/why you're using that label.

You can use a post-process to add a label automatically, but it would apply to all epics using that workflow. 

It might be possible, using automation and some other conditions (like a specific word) to conditionally detect something in the summary.
For example:
When using that Roadmap view add a keyword to the title, like "ROAD" (for example), then using automation you can detect the keyword and add the label, then modify the title to remove the keyword.

This would be a fairly silly amount of work - and I don't actually advise you do that - but I think it's theoretically possible none the less.

[David Heath]

Thanks Chris, 

we have multiple boards within one project, each board corresponds to a somewhat independent workstream. We separate those out using labels. For this particular workstream I want to plan out at an epic level. 

Perhaps we should be using projects instead of boards split out by label?

[Chris Buzon]

That might end up being a better fit for you, since the boards themselves can easily handle multiple projects and workflows, you might find the project level separation gives you a bunch of flexibility.

It's certainly not required, but I think that the benefits would outweight the setup costs.  If you need to change something like security permissions, having separate projects will save you a huge amount of hassle.