nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Spike has the same fields than Story. How can we customize it?

Yolinda Burns

Our team has elected to incorporate Spikes into our process as our analysis and previous institutional knowledge suggest that Spikes are more succinct and intended specifically for exploratory purposes, in contrast to Stories. We have tailored our Stories with numerous custom fields that we prefer not to apply to Spikes. However, upon creation, we've noticed that the Spike inherits the same fields as a Story. Could you provide guidance on how to streamline the Spike by eliminating these superfluous fields?

Accepted answers

Trudy P Claspill

Hello @Yolinda Burns

Welcome to the Atlassian community.

Are these Spike issues in a Company Managed project or a Team Managed project? You can find that information in the Type column on the View All Projects page under the Projects menu.

The method to customize the fields that display is different between the two types of projects.

All comments

Trudy P Claspill

Hello @Yolinda Burns

Welcome to the Atlassian community.

Are these Spike issues in a Company Managed project or a Team Managed project? You can find that information in the Type column on the View All Projects page under the Projects menu.

The method to customize the fields that display is different between the two types of projects.

Yolinda Burns

Thank you for the quick response! its "Company-managed software"

Trudy P Claspill

For a Company Managed project there are a couple of things that impact the fields that are available. Note that unless otherwise stated, changes to any of these can be done only by a Jira Administrator - not by a person who is only a Project Administrator.

There is a Field Configuration Scheme associated with the project. In that Scheme there are Field Configurations that are associated to the issue types used in the project. In the Field Configuration you can set fields as Required or Optional, and you can set fields as Hidden or Shown. The setup of the Field Configurations and the Field Configuration Scheme can be seen from Project Settings > Issues > Fields.

If you want to change those settings for the Spike issue type that would involve creating a new (or copying an existing) Field Configuration, adjusting the settings in it, and then adding that Field Configuration to the Field Configuration Scheme for the project and mapping it in that scheme to the Spike issue type.

Note that if the Field Configuration Scheme is shared with other projects, that could impact the Spike issue type in those other projects also.

Next there are Screens that define fields that will be available. Screens are mapped to the three issue Operations (Create, Edit, and View) in Screen Schemes. Screen Schemes are associated to Issue Type in Issue Type Screen Schemes. It is the Issue Type Screen Scheme that is associated to a project. The setup of these items can be seen from Project Settings > Issues > Screens.

If you want to change the fields that present on screens for the Spike issue type that would involve creating a new (or copying an existing) set of Screens, adjusting the fields on those screens, then creating a Screen Scheme to associate those screens to Issue Operations. Then you would add that Screen Scheme to the Issue Type Screen Scheme mapping it in that scheme to the Spike issue type.

Note that if the Issue Type Screen Scheme is shared with other projects, that could impact the Spike issue type in those other projects also.

The last thing to consider is the Issue Layout. The Layout can be used to change the fields that display when you are viewing an issue. This can be changed by a Project Administrator, but is limited to operating with the fields that are Shown within the Field Configuration that is used for a given issue type.

Let me know if you have additional questions after reviewing that information.

Yolinda Burns

Thank you SO much! We will escalate the request to our Jira Administrator. I appreciate your detailed and very informative response!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

card