...
We are using Atlassian’s Cloud toolkit Forge for developing Agile Hive Cloud, which results in us being technically bound to Forge’s feature set. Forge is not as mature as other development toolkits (above all compared to DC), hence some things might just not work at all, until Atlassian fixes issues with Forge or extends it’s functionality. On this page, we want to document such scenarios and explain them technically.
Default Jira Views
In the sections below, you can find more information on technical limitations that may impact functionality and / or displaying of Agile Hive-related data in default Jira views (e.g., Backlog, Sprint Board, JQL search results…).
Custom Field: Assigned PIs
Added on
Agile Hive comes with the predefined Custom Field ‘Assigned PIs’ that is used to assign issues of type Objective or Risk with one or more PIs. Agile Hive stores this information as a list of IDs of assigned PIs in the Forge Storage of the app. To display the information stored for this field we have to distinguish two cases:
For the Jira Issue View sidebar, there is a way to render Custom Fields that store data in Forge Storage. Agile Hive is capable of displaying all assigned PIs for an issue.
For other Jira views (e.g., Backlog, Sprint Board, JQL search results…) Atlassian does not offer a way to properly render Custom Fields that read data from Forge Storage. This results in those views displaying the ID values of assigned PIs instead of the PI name.
Currently, there is no workaround available to apply a fix to this behavior. In case you need to display information on assigned PIs in various Jira views you can leave a vote for the corresponding issue at Atlassian: https://ecosystem.atlassian.net/browse/FRGE-135
Reports
In the sections below, you can find more information on technical limitations that may impact functionality of Reports in Agile Hive for Jira Cloud.
...