Stintwise runs entirely on Atlassian's platform, with no servers of its own. If the tile fails for everyone at once, look at Atlassian's status pages first:
- Jira
- Atlassian Developer Status, which covers Forge, the platform Stintwise runs on
One alert rule watches the production app. Atlassian's developer console emails the developer when, over one hour, the share of the app's invocations that succeed falls below 95%, as major, or below 80%, as critical. It watches nothing else: not the figures the tile states, so a chart that loads with a wrong number raises no alert. Nor does it see a chart that fails to build or a tile that cannot reach Jira: the tile says so in its own message, and Atlassian counts as failures only errors the app does not catch, timeouts and running out of memory. The alert is an email, and a person then reads it. A problem in Stintwise itself that affects everyone is added under Known issues once the developer knows of it, and the changelog says when it is fixed. A view withdrawn for a wrong number is listed under Known issues too, until its fix ships (what withdrawn means).
Replies
Replies to email follow the times on the support page. When they are paused, this section says so beforehand, with the dates.
Known issues
Each of these is recorded, to be fixed when its part of the app is next changed; no date is promised, except for a view withdrawn for a wrong number, whose time to a fix is on the support page. Smaller ones, such as a tooltip that wraps one word onto a line of its own, are not listed here.
- Reproduced from the ledger CSV, a By status row can, rarely, read one step more or less than the tile where two rows lose exactly the same in rounding: the CSV's hours, to four decimals, cannot settle a tie the tile settles in whole seconds (how the rows are rounded).
- In Aging, a column too narrow for its
· N past 85%drops it, so one column can show that count while the next does not. - On the very first view after the app is installed, the tile can stay blank for about 40 seconds before the chart appears.
Not yet checked on a real Jira site
Built and tested, and not yet checked on a real site:
- the widget for Jira's new dashboards: status names with characters such as &, — or é in its settings, what each viewer's browser is sent with it, Medium and Large rows, browser windows narrower than 1,728 pixels, and its licence check (adding it and its settings, a refused save, the chart drawn again after Save, the dark theme, a work item opened from a drill panel, Export data (CSV) and Copy text are checked); use a classic dashboard until this line goes;
- Show and Compare on a filter that spans several issue types or projects;
- pressing a row of saved filters side by side, Export saved filters (CSV), the table's Image or summary opened, the comparison with the period before on the table once Compare with … is ticked, and its image and summary, and Add a saved filter or project, or type JQL in the settings;
- the four quarters on the table of saved filters side by side: Compare with … ticked after them building nothing new, the table's image and summary opened before the tick gaining the quarters and losing them on an untick, the table at a 304 px column and in Jira's dark theme, a project's and a typed JQL query's quarters, a colleague shown the quarters once Jira confirms that their searches return the same work items, and the quarter before a chart of Last full quarter built on two days in a row, the second from the first (the quarters, each row's two quarter exports, and the table's image and summary stating them, are checked);
- a tile of several saved filters whose settings someone else changes while it is open, and Reload the dashboard;
- a new project's own Done status counted in the next chart built once work has moved through it;
- two people with different access each seeing only their own chart;
- a chart shown to a colleague after Jira confirms, as them, that their own searches return its work items, and built again for one whose searches differ;
- the rows of saved filters side by side shown the same way, and a row waiting for a colleague's chart with no figures;
- a chart's next build that reads again only what changed: what it costs of Jira's hourly limit, an issue type renamed, a sprint closed, and how long Jira's search takes to show an edit;
- a chart built on a Friday whose first view on the Monday after starts from the Friday's build;
- the statuses of work finished after a chart's range, and your Started statuses, in Export data (CSV): three work items' statuses at a day's end traced in their change history, and what the update's first build costs of Jira's hourly limit;
- flow efficiency on By status: its figure with a queue status unticked, its line with one group shown, and its Started rows with a screen reader;
- natural process limits on the Scatter: with one group shown, on a chart of the last closed sprint, and a ringed dot with a screen reader;
- cumulative flow in the Flow view: its bands against the run charts, beside Jira's own cumulative flow diagram, with one group shown, none offered on a chart of the last closed sprint, and its slider with a screen reader;
- the public holidays of a state or region: a chart of one against its export, and choosing one in the settings by typing its name, in Chrome and Firefox;
- working hours that differ by weekday: a chart counted on them, its figures, method line and drill panel against its Export data (CSV), the fourth choice by keyboard at 304 px and a refused weekday, its saved settings, and a dashboard open since before the update showing its reload line until reloaded;
- days the whole team is off: a chart leaving a listed day out against its Export data (CSV) and its drill panel, and the field by keyboard, a Saturday and 61 dates refused with their lines, and the note under it;
- lead time on the chart: the choice not carried to another browser, and the views in lead time at 304 px and in the dark theme;
- a calendar for each source side by side: a typed query's row, twenty rows at 304 px by keyboard in light and dark, and a table cut to one source with its alert;
- Full screen inside Jira's frame pressed by a person, in each browser, and on the widget;
- the Stintwise actions in a Jira Automation rule: the text a comparison writes, Write a Stintwise summary of several sources, a run that fails and its sentence in the rule's audit log, the form's refusals and the largest settings a rule keeps, the warm-up runs any table needs other than the one counted, six sources of up to 149 work items compared with runs a minute apart, and any table's when they are 15 minutes apart or in an hour when people at their tiles start charts, and a summary sent by email, to Microsoft Teams, to Slack, or as a comment naming a source whose name holds formatting;
- an action whose settings someone other than the person whose connection it uses saves, and a saved filter whose query someone else changes, each stopping the action: it needs a second account on the test site;
- Aging and By status grouped by a board's columns: the words Atlassian shows an administrator for the two permissions, a viewer who cannot open one of the boards, no Group by row on a team-managed project's chart, a grouped export against the face, what one choice costs of Jira's hourly limit, a board's columns changed while the tile is open, and a column's head with a screen reader;
- the download and copy buttons of Image or summary;
- a comparison with the period before that has figures in both periods;
- the Forecast view's controls and the list a day of its strip opens;
- By status in a real workflow's order, the button on the count line, where each panel opens, and Export data (CSV) against a file exported before the update that renamed it;
- the larger targets and the forced colours inside Jira's frame;
- a bar's list exported before and after the update that stored charts more compactly, compared byte for byte;
- the work that finished after a chart's range, which a third search of yours reads when the range
runs to today, and its
since_totalrows in Export data (CSV); - in Aging, the time in status and the stays table against the export, and Measure ages when this view opens;
- the Flow view: one day's work in progress against the export, and its two sliders with a screen reader;
- the 70% line's figure against the export, and the box still ticked after a reload in Jira's frame;
- the charts rebuilt for working days: each one's figures and Export data (CSV) against those before the update;
- a chart counted in working hours: Time counted in the settings, and the chart's figures, words and drill panel against its own Export data (CSV);
- the footer's Time zone, build time and method and the boxes under the chart, inside Jira's frame, an image downloaded before and after that update, compared byte for byte, and a new tile's settings asking which time is counted;
- a work item whose history came from an import: a work item imported and then moved on in Jira, and one moved back to To Do before the import on a chart beside one that shows the import (its rows in Export data (CSV), one in progress aged from its imported start, and one created before the chart's range, found by its resolution date, are checked);
- the settings' Started statuses and Done statuses lists on a site with more statuses than they show at once;
- the charts rebuilt with fewer requests to Jira: a chart's Export data (CSV) against one exported before the update, compared byte for byte;
- the charts built by reading Jira as the person viewing them: a chart's Export data (CSV) against the same chart built by reading as the app, a tile of saved filters side by side whose rows are built this way, and a person Jira will not act as, whose chart is built as before;
- Safari, Firefox and Edge, and a screen reader: on a real site, only Chrome has been used;
- Jira's dark theme in the settings, and in views other than Forecast;
- a project or a typed JQL query refused to someone who cannot open it, and a query's whole text under the footer's switch;
- Image or summary opened while Show or Compare splits the chart by parent, label or component;
- Show a target on saved filters side by side: the Within column beside the period before;
- a parent left blank in Export data (CSV) for someone who cannot open it: on a real site, only the site admin has exported a chart with parents;
- a team's name read from Jira's Team field in Export data (CSV) of a chart across several teams (under Show, in Compare by team, and in the export of a chart of one team's work items, it is checked); and whether the tile names a team to someone Jira would not show it to;
- a sprint's name for someone who cannot see its board: on a real site, only the site admin has viewed a sprint's chart.