Personas custom fields
The Persona custom field, allows a user to associate one of the Personas created in their Project with an issue in Jira. This signifies to the team which of our Personas will be serviced by delivering this piece of work.
The Importance to Persona has 4 variables:
The Importance to Persona custom field allows a users to flag to their team, how important a particular piece of work is to the chosen Persona.
To see and edit these on an issue, they need to be added to an Issue Screen.
For Jira Cloud Software Projects
A Jira Administrator can find the issue view settings in
Jira settings → Issues → Screens.
Find the Project's Screen Scheme(s), eg. "CDDS: Scrum Default Screen Scheme". There may be more than one to configure for your Project, typically a Default and a Bug Screen Scheme.
For each Screen Scheme, go to
Configure (not Edit). To add new fields to the issue view, search for them in the dropdown at the bottom.
Add both the “Persona” and “Importance to Persona” fields to the screen. Users will be able to find and edit these on issues they have permission to edit so that they can link Personas to the issues which that Persona values.
At this point, you can reorder the fields on your screen as well. Fields lower down the list are often hidden under a “Show more fields” link and can be more difficult for users to find.
Next-gen Projects use a separate set of fields to the fields managed in Jira Settings. This means that they can’t use the “Persona” and “Importance to Persona” custom fields created by Easy Agile Personas.
We’re investigating a way to create and use fields in Next-gen Projects but this feature isn’t available yet. While you can still create and manage Personas within a Next-gen Project, they can’t yet be linked to Jira issues.