It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

  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!

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.

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
TAGS
Community showcase
Posted in Agile

Overview of Advanced Roadmaps UI + Get started with Automation for Jira - Demo Den September 2020

Deliver better and faster value to your customers with the Jira automation platform. Watch this Demo Den series below to learn how to use the new interface and set up automation rules to help your te...

1,292 views 3 6
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you