Epic/Theme field but ... how to use Themes in SCRUM template?

[Mirek]

Hi,

My question is simple...

I want to use the GreenHopper and build in SCRUM template. If I accept this template to my project I see that there is a field named Epic/Theme that I can use for example to link Epics/Themes with Stories, right?. The problem is that there is no issue type named Theme in GreenHopper Scrum Issue Type Scheme.There are only 5 issue types available: Bug, Improvement, Epic, Story and Technical Task (that is as Sub-Task)

Can anyboody can answer me why I have a field named Epic/Theme but I cannot use Theme issue type in SCRUM Template?

I know that I can make my own Issue Type Scheme and add there a Theme, but when I will use it I will not be able to use SCRUM template anymore. (SCRUM Template have some OOTB functionality that Default templates dosn't have)

If you are using GreenHopper and Themes.. How you are caputring them for your project?

Thanks,

Mirek

[Mirek · Accepted solution]

Currently we are creating Epics with a 'THEMES' component

In addition we are adding THEME: prefix in the summary in every Epic that should be tracked as a Theme..

That give us ability to quicly search, find wanted Themes and link to other tickets using Epic/Theme functionality.

-Mirek

[Stephen Kerman]

Just start typing - it will create new Themes on the fly from your input

[Emmett]

How do I enter my own themes into the THEME field? The field comes up blank in issues... very annoying

[AndyAtTogether]

As i understand it, epics and themes are different.

Epics are large requirements that will be broken down into stories as and when required wheras a theme groups stories (and potentially epics i suppose) by cross cutting them, in that respect themes could easily cross sprints.

what about using components to track themes?

[Mirek]

Hi andydavo..

Yes .. you are right.. Using components it is a good way also and we choose already that way in the past..

-Mirek

[AndyAtTogether]

what about using components to capture themes?

[gauravkohli]

We use Epic Issue type to create Epics and then use "Epics/Themes" field to link stories to the Epic created using Epic issue type.

Epics & Themes are used interchangebly in Greenhopper ( someone can check this assumption )

[Renjith Pillai]

And GH also allows to have themes, which need not be necessarily issues created, but kind of a label which can denote which theme the issue belongs to.

[Mirek]

Renjith,

So what is your proposition of using a label to capture a Theme?

I am having for example below Themes:

• Managing Project Budgets
• Managing Program Details
• ...

And I want to connect them to some Epics that are connected to stories using OOTB Epic/Theme field.

Should I create a new customfield named "Theme" (label type) add it to the project (will this not break OOTB Scrum Templete?) or there is another option that I am not aware of?

Could you show a quick example?

[Renjith Pillai]

I don't think you need to create a new custom field. The same Epic/Theme field accepts both jira issues and labels of your choice.