Comment on page
Fields added to screens
Ativo Programs automatically adds some fields to screens for Jira projects used in Ativo Programs.
There is a limitation in the Jira API used by Ativo Programs. In order for a user to update information on a field, the field must be present on a screen. So as to ensure a user is able to update a field in Ativo, this field must be visible on screen.
Ativo Programs checks that the field is present on the screen, and adds it if not yet present.
For teams working Kanban, the Due date is added on the main tab (unless if it is already present in another tab).
For epics in scope of a program, the Story Points field is added on the main tab (unless if it is already present in another tab).
For teams estimating in Story Points, the Story Points field is added on the main tab (unless if it is already present in another tab).
The fields are added to related Jira projects when saving the teams or program configuration in Ativo programs.
In Ativo Programs, go to Settings > Teams and Settings > Program to update the teams and program configuration.
Screens are updated for Jira projects used in Team and Program configurations.
Ativo Programs first checks the issue type screen schemes that are related to the project.
It then check the screen schemes that are related to the issue type screen schemes
Finally, it adds the fields to the screens that are related to the screen schemes.
Note: depending on the Jira configuration and shared use of issue type screen schemes, screen schemes and screens, this could mean that screens from Jira projects not being used inside Ativo Programs receive additional fields.
Ativo Programs checks if the field is already present on a screen before adding it.
Note: version 2.5.0 includes a bug fix to also check other tabs on the screen for the presence of a field.
An error will be shown if you're updating an issue that requires an Ativo custom field, but without the field being on a screen. This can happen if Ativo was not able to add the custom fields to the screens (*), or the field was manually removed from a screen.
Error while updating issue. Field 'customfield_xxxx' cannot be set. It is not on the appropriate screen, or unknown.
(*) Due to a bug, this could have happened on Jira cloud for newly created programs and teams between November 19th and December 4th 2023.
To mitigate, as an Ativo Admin:
- open the Team configuration page and click submit (no need to change anything on the page)
- open the Program configuration page and click submit (no need to change anything on the page)