why use the Greenhopper issue type scheme vs the default one?

What is the benefit of this vs. customizing the default scheme?

Also in the Agile section under configuration, you have to choose a project template? What is the benefit of selecting the scrum template here?

3 answers

This widget could not be displayed.
  1. The issue types, Epic, Story and Technical Task gets associated with the project the GH scheme.

Read the section "About the 'Scrum' Template" from http://confluence.atlassian.com/display/GH/Specifying+your+Project+Templates

I have a related question that was sprouted after this posting answered my original question like the OP.

If the Scheme applies the additional fields, why doesn't the issue types have the custom fields applied when used in other schemes? Such as Story issue type and the Story Points custom field? I can associate the custom field but the field will only show in standard JIRA view but will not display when creating a new card in the Greenhopper/Agile view.

I suppose they must have some underlying custom files that dictate what fields show in what view for what scheme. I would have expected a Greenhopper screen but it uses the default and possibly uses vm files to interject the custom fields on the card screen.

I hope that made sense. Maybe this is an enhancement request to Atlassian.

What fields are shown in the GH cards can be customized as described here http://confluence.atlassian.com/display/GH/Configuring+your+Card+Styles

Thanks Renjith!

This widget could not be displayed.

I have a related question that was sprouted after this posting answered my original question like the OP.

If the Scheme applies the additional fields, why doesn't the issue types have the custom fields applied when used in other schemes? Such as Story issue type and the Story Points custom field? I can associate the custom field but the field will only show in standard JIRA view but will not display when creating a new card in the Greenhopper/Agile view.

I suppose they must have some underlying custom files that dictate what fields show in what view for what scheme. I would have expected a Greenhopper screen but it uses the default and possibly uses vm files to interject the custom fields on the card screen.

I hope that made sense. Maybe this is an enhancement request to Atlassian.

This widget could not be displayed.

I have a related question that was sprouted after this posting answered my original question like the OP.

If the Scheme applies the additional fields, why doesn't the issue types have the custom fields applied when used in other schemes? Such as Story issue type and the Story Points custom field? I can associate the custom field but the field will only show in standard JIRA view but will not display when creating a new card in the Greenhopper/Agile view.

I suppose they must have some underlying custom files that dictate what fields show in what view for what scheme. I would have expected a Greenhopper screen but it uses the default and possibly uses vm files to interject the custom fields on the card screen.

I hope that made sense. Maybe this is an enhancement request to Atlassian.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 21, 2018 in Agile

What's new this quarter in Confluence Server - August 2018

Hello Atlassian Community! My name is Ada , and I'm the Product Marketing Manager for Confluence Server at Atlassian. If you missed   our last post, we're transitioning to quarterly updates&nb...

116 views 0 1
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you