The following properties have a default mapping between
JIRA Agile and
Silk Central:
- User stories that are in
JIRA Agile's
Backlog are reflected in
Silk Central by having the
Sprint property value set to
Backlog. This enables you to easily search for them by creating a filter.
- The default
Priority values of
JIRA Agile's user stories are mapped to
Silk Central's
Priority property. If you are not using
JIRA Agile's default
Priority values, you can customize this mapping.
Viewing
JIRA Agile Backlog Stories in
Silk Central
- In the menu, click
.
- Create a new filter with the following criteria:
- Selection Criteria:
External Custom Attributes
- Property:
Sprint
- Value:
Backlog
- Click
Apply to apply the filter immediately or
Save and apply to save the filter for future reuse.
Mapping
JIRA Agile Priority values to
Silk Central's Priority
The default
Priority values of
JIRA Agile's user stories are mapped to
Silk Central's
Priority property as follows:
- Blocker=SC_Priority_Critical
- Critical=SC_Priority_High
- Major=SC_Priority_Medium
- Minor=SC_Priority_Low
- Trivial=SC_Priority_Low
If you are not using
JIRA Agile's default
Priority values, or if you want to customize the mapping, your
Silk Central administrator should customize the settings as follows:
- Stop the application server.
- Open the file
propertyMappings.properties with a text editor. This file is located in the
JIRA Agile plugin-file
JIRAAgile.zip on the application server in the
plugins folder.
- Search for
SC_Priority=Priority, beneath which you can customize the mapping of
JIRA Agile's
Priority values to
Silk Central's
Priority.
Note: Silk Central
Priority values require the prefix
SC_Priority_.
- Save and close the file
- Re-start the application server.