Support for Atlassian Server Products (and apps like BigPicture) is has ended in February 2024.

Are you planning a migration to Cloud? Make sure you don't lose your BigPicture data/configurations in the process. Check out this page for information on how to migrate BigPicture's data to Cloud. If you have any questions please email support@appfire.com

Story points field

Story Points Field

The Story Points field can be mapped to various other numerical value fields. Mapping can be configured per the Jira Project. By default, the field is mapped to the native Story Points field in Jira. 

In the drop-down menu, the App offers you a variety of existing fields with a numerical value - that doesn't mean each possible mapping will suit your needs. Make sure that the mapping meets your business needs.

For example:

If you mapped "Story Points" to "Time Tracking Progress (Original)," a built-in Story Points field value for a new task would be 0, and for a finished task, it would be 100 story points.

When the Original Estimate is 2d and the time logged is 1d, the value of the built-in Story Points field will be 50.

  • The Story Points field in a column/card view can display values stored within multiple fields (e.g., from various team-managed projects).

  • The Story Points totals in the Board module (capacity allocation, work progress) can be calculated based on selected fields.

The Story Points built-in field, aggregating data from mapped fields, can be added to the column/ card view.

Not Synchronized

When selecting the "Not Synchronized" option, the App will use the default Jira "Story Points" field for all operations. The built-in "Story Points" field will display the same value as the Jira "Story Points" field in:

  • Column/Card views

  • The Resources module (Workload Contouring, Story Point mode)

The system will display no value if the Jira "Story Points" field hasn't been added to the screen scheme. Operations such as workload contouring won't be available, and the system will show you a warning, letting you know Story Points haven't been configured and can't be used. 

Mapped

The App uses the built-in field value for all operations (workload contouring, resource planning in story point mode, etc.)

After the mapping,  even if the Jira "Story Points" field has been added to the Jira screen and has a value, the App will use the mapped field value for all operations (for example, in the Resources module in Story Points mode and for workload contouring).

For columns/card views, you can select if you want the system to display a Jira "Story Points" field value or the built-in "Story Points" field value. 

Custom Field

You can create a custom numerical field in your Jira and add it to the screen scheme. The field will be available in the Technical configuration drop-down menu and can be used for mapping.

To add a custom field, go to Jira configuration (cog at the top right) > Issues > Custom Fields (on the left) > Add custom field (button at the top right).

The field has to have a numerical value. 

Remember to add the field to the screen scheme(s) used by projects where you want the field to be available.

On the App Configuration > General > Fields page, you can use the custom field for mapping - either for the entire application or various projects.