Skip to main content

Custom widget builder

Overview

The custom widget builder lets you assemble a dashboard widget yourself instead of picking one off a fixed list. You choose what the widget counts, filter it, group it, split it, calculate with it, and decide how it is drawn — so a reporting question that no predefined widget answers can still become a widget.

​

Anything you build is saved to your workspace's widget library, where every user in the workspace can find it and add it to their own dashboards.

​

​

Starting the builder

Open the dashboard you want the widget on and click + Add widget. The button now opens a short menu with two routes: Browse widget library for widgets that already exist, and Create custom widget to build a new one.

​

The + Add widget button opened, showing the Browse widget library and Create custom widget options

​

The builder opens empty, with Choose at least one entity to retrieve data on the canvas. Everything you configure on the left is redrawn on the right as you go, so you are always looking at the real result rather than a preview of a template.

​

​

Building the widget

1. Pick what the widget counts. Click + Add entity and choose Test case, Run result, Defect, Test run or Requirement. A widget can hold up to five of these blocks.

​

The Add entity menu listing Test case, Run result, Defect, Test run and Requirement

​

Each block is lettered — A, B, C — and the letter is added to a series name when two series would otherwise read the same. Two blocks of different entities already look different in the legend, so they carry no letters; two blocks of the same entity become Case: High (A) and Case: High (B).

​

2. Narrow it with filters. Click + Filter by under the block and choose a field, then tick the values you want. The list holds the entity's own fields — author, priority, severity, type, status, automation status — alongside the custom fields defined in your projects.

​

The Filter by field list open on a test case block, showing Author, Priority, Severity, Type, Status and Automation status

​

Ticking several values on one field matches any of them, and the filter then shows the first value with a counter — Severity: Medium +1. Filters on different fields all have to hold at once, so adding a second filter always narrows the block further.

​

3. Group the results. Click + Group by and choose the field that becomes the axis of your chart or the first column of your table. Grouping is what turns a single number into a distribution: group test cases by author and you get one bar per author instead of one total. The menu runs the entity's own properties — author, status, priority, severity, suite, tags, milestone, layer and the rest — followed by your projects' custom fields.

​

The Group by menu open on a test case block, listing the fields the block can be grouped by

​

Each block takes one grouping. Once you have chosen it the + Group by button greys out; remove the chip to pick a different field.

​

4. Add a second block to compare. Click + Add entity again. The second block is configured exactly like the first, and both are drawn on the same chart.

​

The builder with a Test case entity A filtered to high severity and a Defect entity B filtered to medium severity, drawn together as a bar chart

​

This is where the builder earns its keep. The two blocks do not have to be the same kind of thing — high-severity test cases against medium-severity defects, as above — and they do not have to be different kinds either. Adding Test case twice with different filters is how you compare two slices of the same data side by side.

​

​

Splitting every block by a property

A segment cuts across the whole widget. Where a block's own grouping shapes that one block, a segment applies to every block at once and splits each of them by the same property — so you can ask "these two counts, broken down by priority" without configuring the breakdown twice.

​

Click + Add segment under Segment by and pick the property. Each segment then carries its own filter, so you can restrict it to the values worth comparing rather than every value the field has. Segments are numbered 1, 2, 3, where blocks are lettered, and a widget can hold up to ten.

The menu only offers properties that every block in the widget can express, because a segment has to mean the same thing in all of them. If your blocks share no property the button is disabled — requirements, which carry no properties, are the common cause. For the same reason, once a segment is in place you cannot add a block that has no such property until you remove the segment.

​

​

Which projects the widget covers

All projects is ticked by default, under Segment by. Left as it is, the widget draws on every project the dashboard itself is set to — so the same widget shows different data on a dashboard scoped to one project than it does on a workspace-wide one.

​

Untick it and a project picker appears, and the widget is then pinned to the projects you name there whatever the dashboard is set to.

​

​

Calculating with formulas

A formula turns the blocks into a calculated figure — a pass rate, a ratio, a difference — instead of drawing each count on its own. You refer to each block by its letter: ENTITY(A) is the count from block A, ENTITY(B) the count from block B, and so on.

​

Open the Formula section, below Segment by, type the formula and click Apply formula. As soon as you type ENTITY(, a list of the blocks on the widget opens, each with its letter and entity, so you can pick the right one without scrolling back up.

​

The Formula box with ENTITY(D)/ being typed, and a list offering ENTITY(A) Test case, ENTITY(B) Run result, ENTITY(C) Defect and ENTITY(D) Run result

​

An example: the pass rate. Block B counts every run result, and block D counts run results filtered to Status: Passed. The formula ENTITY(D)/ENTITY(B)*100 divides passed results by all results and multiplies by 100, which gives the pass rate as a percentage.

​

Once a formula is applied, the widget draws only its result. The blocks still supply the numbers, but their own bars or lines leave the chart, and the legend names the formula instead. Remove, beside the Formula title, takes the formula off and brings the blocks back.

​

The builder with ENTITY(D)/ENTITY(B)*100 applied: the chart shows a single bar for the formula, the legend names the formula, and the # and % buttons sit beside Render as

​

​

Writing a formula

To use

Write

Example

A block's count

ENTITY( and the block letter, A to E

ENTITY(A)

A number

A whole number, or a decimal with a dot

100, 0.5

Addition and subtraction

+ and -

ENTITY(A)-ENTITY(B)

Multiplication and division

* and /

ENTITY(A)/ENTITY(C)*100

Grouping

Parentheses, which can be nested

(ENTITY(A)+ENTITY(B))/2

Several results at once

Formulas separated by ;

ENTITY(A)/ENTITY(C)*100; ENTITY(B)/ENTITY(C)*100

​

Multiplication and division are worked out before addition and subtraction, and operators of the same kind run from left to right — so ENTITY(A)+ENTITY(B)/2 halves only B. Add parentheses whenever you mean something else.

​

Capital letters and spaces make no difference: entity(a) / entity(b) works as well as ENTITY(A)/ENTITY(B). A decimal needs a digit before the dot, so write 0.5 rather than .5, and a number cannot be written as a negative on its own — subtract it instead.

​

Each formula separated by ; becomes its own series, named after the formula in the legend. Together, all the formulas and the semicolons between them can be up to 255 characters long.

​

If Qase cannot read the formula, Formula cannot be parsed. appears under the box. A letter that matches no block on the widget gives Formula contains an invalid entity. instead.

​

​

When the formula divides by zero

Dividing by zero gives 0 rather than an error. The exception is a day, week or month in which every block the formula names counts zero: there is nothing to measure, so that point is left empty instead of being drawn as 0. A pass rate over a day with no results shows a gap, not 0 %.

​

​

Showing the result as a percentage

Once a formula is applied, two buttons appear beside Render as: # shows the values as plain numbers, and % writes a percent sign after each of them.

The % button only adds the sign — it does not convert the value. A formula of ENTITY(D)/ENTITY(B) with % on reads 0.14 %, not 14 %. Multiply by 100 in the formula itself, as in ENTITY(D)/ENTITY(B)*100, and then switch % on.

​

​

What a formula cannot be combined with

A formula works on one total per block, so it cannot be combined with anything that splits a block into several values:

  • Group by. With a formula applied, + Group by greys out on every block; with a grouping in place, the Formula section is unavailable.

  • Segments. The same rule applies to + Add segment.

  • Donut chart. A donut does not show formulas, so it greys out in the Render as list once a formula is applied, and Apply formula stays disabled while a donut is selected.

​

To switch from one to the other, remove the formula, the grouping or the segments first.

​

​

Choosing how it is drawn

Render as sets the visualisation: Bar chart, Line chart, Donut chart, Table or Single value. Switching between them keeps your blocks, filters, grouping, segments and formula intact, so it costs nothing to try each one.

​

The Render as list open, showing Bar chart, Line chart, Donut chart, Table and Single value, with Single value selected

​

A line chart adds an Accumulated total checkbox. Left unticked, the lines plot what was created in each bucket — the activity in the period. Tick it and they plot the population instead: how many of that entity existed at each point.

​

A line chart with Accumulated total ticked, and a hover tooltip listing each series and its value for one day

​

A table gives one row per group and one column per block, headed with the block's filter — so CASE: HIGH (A) and CASE: HIGH (B) sit next to each other and the comparison reads straight across.

​

A table widget with one row per author and separate columns headed CASE: HIGH (A) and CASE: HIGH (B)

​

A donut chart adds a Show labels checkbox, on by default, which writes each slice's name and value around the ring instead of leaving them to the legend.

​

A donut chart with Show labels ticked, each slice annotated with its entity, filter and count

A donut chart shows one entity. It is available only while every block in the widget is the same entity — several blocks of test cases are fine, because they are slices of one population, but a block of test cases beside a block of defects would add unrelated things into one ring. Mix two entities and the donut greys out in the Render as list; choose the donut first and the + Add entity menu stops offering the other entities.

The Render as list with Donut chart greyed out because the widget holds two different entities

​

A single value shows each series as one large number on a card of its own — the quickest way to put a headline figure, such as the current pass rate from a formula, on a dashboard. Use it with the Now period: over a longer period each series holds a value per day, week or month, and the widget then shows them as a table instead. A single value needs one number per series, so it is unavailable while any block is grouped or the widget has segments.

​

​

Setting the period

The two controls in the top-right corner decide the span of data. The first sets the bucket size — Daily, Weekly or Monthly — and the second sets the window: Now, Last 7 days, Last 14 days, Last 30 days, Last 3 months, Last 6 months or Last 12 months.

​

The period list open, showing Now, Last 7 days, Last 14 days, Last 30 days, Last 3 months, Last 6 months and Last 12 months

Now is a snapshot with no time axis, so a line chart has nothing to plot along the bottom. The line chart therefore leaves Now out of the list, and switching to a line chart while Now is selected moves the widget to Last 30 days.

​

​

Saving the widget

Click Add to dashboard and give the widget a Widget title, which is required and holds up to 255 characters, and an optional Description of up to 1000.

​

The Add widget to dashboard dialog with the Widget title and Description fields and a note about the widget library

A custom widget belongs to the workspace, not to the dashboard you built it on. Saving it puts it in the widget library, where every user in your workspace can see it and add it to their own dashboards. Give it a title that will still mean something to a colleague who was not there when you built it.

​

​

Reusing a custom widget

Custom widgets live alongside the predefined ones. Click + Add widget, then Browse widget library, and pick the Custom widgets category — or search for the widget by name.

​

The widget library with categories By entity and By type down the left, including a Custom widgets category

​

A widget the dashboard already holds cannot be added to it twice — its button is disabled and says so.

​

​

Editing a custom widget

Open the three-dot menu in the widget's top-right corner on the dashboard. Edit reopens it in the builder, Duplicate makes an independent copy, and Remove from dashboard takes it off this dashboard.

​

A dashboard widget's menu open on Duplicate, Edit and Remove from dashboard

​

Once you change anything, the label beside the widget's name turns from Saved to Edited and the Update button becomes active. Confirming the change opens a dialog where you can also revise the title and description.

​

The Update widget dialog, warning that the updates will be applied to all widget instances

Updating a custom widget changes it everywhere it is used. If three dashboards across the workspace carry it, all three change, including other people's. When you want a variation rather than a correction, use Duplicate first — that makes a genuinely separate widget with its own entry in the library — and edit the copy.

​

​

Deleting a custom widget

Remove from dashboard only unpins the widget from that one dashboard. The widget itself stays in the library and on every other dashboard that uses it.

​

To delete the widget outright, open Browse widget library, find it under Custom widgets, and use the three-dot menu on its card. Qase asks you to confirm and tells you how many dashboards it will disappear from. Deleting cannot be undone.

​

Editing and deleting a custom widget follow the same workspace permissions as dashboards, so a role that cannot save or delete dashboards will not see those options.

​

​

FAQ

Who can see a widget I build?

​

Everyone in your workspace. A saved custom widget goes into the shared widget library, not into your dashboard alone. The data each person sees still respects their own project access.

​

Does editing a custom widget affect other people's dashboards?

​

Yes. A custom widget is a single object used in many places, so an update reaches every dashboard it sits on. Duplicate it and edit the duplicate when you only want to change your own copy.

​

Why is the donut chart greyed out?

​

Either the widget holds more than one kind of entity, or a formula is applied. A donut divides a single whole into slices: two different entities are not one whole, and a calculated figure is not a part of one. Remove the extra entity blocks or the formula, or pick a bar chart, line chart, table or single value instead.

​

Can I show a pass rate on a dashboard?

​

Yes. Add a Run result block, then a second Run result block filtered to Status: Passed, and apply a formula that divides the second by the first and multiplies by 100 — for example ENTITY(B)/ENTITY(A)*100. Switch on %, and choose Single value with the Now period for one headline number, or a line chart to follow the rate over time.

​

Why does my percentage show 0.14 % instead of 14 %?

​

The % button only adds the sign; it does not multiply the value. Add *100 to the end of the formula.

​

Why are Group by and Add segment greyed out?

​

A formula is applied. A formula needs one total per block, so it cannot be combined with grouping or segments. Remove the formula to use them.

​

Can I build a widget on test plans?

​

No. The builder covers test cases, run results, defects, test runs and requirements. Test plans are not among the entities it offers.

​

Are the predefined widgets still there?

​

Yes. They are unchanged and now live under Browse widget library, still grouped by entity and by type. See Dashboards for what each of them shows.

​

Can I build a widget from a QQL query instead?

​

Yes, that is a separate route. See QQL Widgets for pinning a saved query to a dashboard as a table or a chart.

Did this answer your question?