Widget | Aggregated view of a Jira query (sorted list)
I would like to have a widget/tile that will show an aggregated view of a Jira query/filter in a form of an ordered list.
-
[ ] Admin can set a static header for the widget
-
[ ] Admin can define a query sent to Jira
-
[ ] Admin can define a Jira attribute (e.g. name of the Jira field or Jira label) by which to aggregate the results returned from Jira
-
[ ] Admin can define a mapping of the Jira attributes to labels displayed by the widget (e.g. Jira labels must be mapped to user-friendly labels)
-
[ ] Admin can decide if the number of items in each set is displayed or not
-
[ ] Admin can define the number of the top sets to be displayed
-
[ ] User can see the header and a sorted list of items
-
[ ] A single item in the list represent a single subset of results returned from Jira
-
[ ] A single item in the list consists of a label (mandatory) and a number (optional)
-
[ ] Item's label is a user-friendly version of the Jira attribute used to filter out the particular subset of results (e.g. person's name or Clan name)
-
[ ] The optional number is the number of items in the particular subset of all results
-
[ ] Widget will send a single request to Jira
-
[ ] Widget will aggregate the response into buckets
-
[ ] Widget will sort the buckets by the number of results in each bucket
Link to Jira API: https://docs.atlassian.com/software/jira/docs/api/REST/8.5.3/#api/2/search-search
- Widget sends a single request to Jira
- query is authorable
- Jira responds with a single array of items (tickets)
- Widget extracts the single selected field from all the items from the response
- selected field name is authorable
- Based on the array created in the previous step, widget creates a map (unique field value -> number of instances in the array)
- Widget sorts the tuples by the number of instances in each tuple
- Widget displays the list of tuples in the form of a table
- each row consists of a label and a number, both values are taken from the tuple
- label should be authorable, i.e. there should be possibility of defining the map from raw field value into user-friendly label
- "number of instances" column is optional (then we have only one column in the table)
- number of displayed rows is authorable