Themes

Themes

You can now pick your own colors!

What's Changed

• update resizing by @DavidNic11 in #297
• [TR-208] Fix issue type dropdown not having options when no JQL by @bmomberger-bitovi in #284
• reactified by @DavidNic11 in #283
• Updating-action-reference by @LeoDiazL in #299
• Tr 189 implement theme coloring by @DavidNic11 in #298
• Fix a misplaced brace in route-data by @bmomberger-bitovi in #300

Full Changelog: v0.10.1...v0.11.0

Sticky Headers, Group By Fixes, and Title Fix

Overview

The browser will now properly say Status Reports for Jira and when you scroll, the quarter headers are now sticky:

What's Changed

• Tr 215 make the table header sticky and fix the scrollbar margin by @DavidNic11 in #293
• [TR-211] Clean up components using route data by @bmomberger-bitovi in #294
• Fix errors when setting Group By in View Settings by @bmomberger-bitovi in #295
• updates the title and some of the social tags by @justinbmeyer in #296

Full Changelog: v0.10.0...v0.101.1

Fixed Comparison Dates & Rounding

Fixed Comparison Dates

Instead of a relative date (like 15 days ago), you can now select a fixed comparison date. This allows you to build a report that always compares to a specific time (like the start of a quarter).

When a fixed comparison date is selected, the date will be bold instead of the relative time as follows:

Rounding

In the View Settings, you can now round dates to a particular time period:

Rounding will:

• round a start date to an earlier interview
• round a due date to a later interval

For example, if you round dates to Month, then an epic with a due date of Jan 30th will have its end date show as Jan 31st. Similarly, an epic with a due date of Jan 1st will also have its end date be Jan 31st.

Furthermore, rounding also works with status coloring. For example, if you round dates to Month and an epic moved from Jan 1st to Jan 31st, it would not show it as Behind. Only if the epic's due date moved into February would the epic status be Behind.

What's Changed

• TR-159: Previous name for a report is shown when editing the name for a subsequent report by @binaryberserker in #250
• A step forward towards improving the folder organization by @justinbmeyer in #251
• Poc/routing by @DavidNic11 in #254
• TR-105: Change the sidebar and top bar depending if the PLUGIN or the WEBAPP by @binaryberserker in #253
• dev docs by @DavidNic11 in #252
• Canjs folder refactor by @justinbmeyer in #256
• uses replace state on the slider by @justinbmeyer in #257
• starts enabling expanding children by @justinbmeyer in #258
• TR-162: Don't do O(n^2) over large data by @binaryberserker in #255
• Hiding the children in the appropriate way by @justinbmeyer in #259
• update verbiage by @DavidNic11 in #260
• [TR-137] Hide "View Settings" button when user is logged out by @bmomberger-bitovi in #262
• naming updates by @DavidNic11 in #261
• fix app key by @DavidNic11 in #263
• bitovi.tools by @DavidNic11 in #264
• Rounded Corners, Shadows, and fixes #266 by @justinbmeyer in #269
• project clone updates by @DavidNic11 in #272
• url by @DavidNic11 in #274
• TR-178 - Basic e2e tests & pipeline setup by @cbass2404 in #275
• Centralizing the Timeline Configuration's routing state by @justinbmeyer in #273
• add login check by @DavidNic11 in #277
• fixes rollup values when they are complete but have no time TR-205 by @justinbmeyer in #278
• [TR-208] Move routing variables from select-issue-type to route-data by @bmomberger-bitovi in #279
• [TR-209] Move URL-linked data elements from select-report-type to route-data by @bmomberger-bitovi in #280
• [TR-207] Move route-linked data from timeline-configuration to route-data by @bmomberger-bitovi in #281
• [TR-137] Hide the settings sidebar when not logged in by @bmomberger-bitovi in #276
• [TR-210] Move route-linked data from select-view-settings to route-data by @bmomberger-bitovi in #282
• Rounding by @justinbmeyer in #286
• enabling the ability to set the comparison to a specific date by @justinbmeyer in #287
• [TR-212] Remove all route data elements from being passed around in timeline-report by @bmomberger-bitovi in #285
• TR-106: Get the paneling layout working right by @binaryberserker in #271
• attempts to fix TR-214 by @justinbmeyer in #288
• Tr 183 create logo icons by @DavidNic11 in #290
• TR-213: Reset the team's form position when a different team is clicked by @binaryberserker in #289
• routing data to static props by @DavidNic11 in #292
• fix scrollbars for plugin by @binaryberserker in #291

New Contributors

• @cbass2404 made their first contribution in #275

Full Changelog: v0.8.2...v0.10.0

Shadows

Shadows are turned on. This will be replaced with outlines shortly.

What's Changed

• TR-159: Previous name for a report is shown when editing the name for a subsequent report by @binaryberserker in #250
• A step forward towards improving the folder organization by @justinbmeyer in #251
• Poc/routing by @DavidNic11 in #254
• TR-105: Change the sidebar and top bar depending if the PLUGIN or the WEBAPP by @binaryberserker in #253
• dev docs by @DavidNic11 in #252
• Canjs folder refactor by @justinbmeyer in #256
• uses replace state on the slider by @justinbmeyer in #257
• starts enabling expanding children by @justinbmeyer in #258
• TR-162: Don't do O(n^2) over large data by @binaryberserker in #255
• Hiding the children in the appropriate way by @justinbmeyer in #259
• update verbiage by @DavidNic11 in #260
• [TR-137] Hide "View Settings" button when user is logged out by @bmomberger-bitovi in #262
• naming updates by @DavidNic11 in #261
• fix app key by @DavidNic11 in #263
• bitovi.tools by @DavidNic11 in #264
• Rounded Corners, Shadows, and fixes #266 by @justinbmeyer in #269
• project clone updates by @DavidNic11 in #272
• url by @DavidNic11 in #274

Full Changelog: v0.8.2...v0.9.2

Status Reports for Jira

What's Changed

• [TR-137] Hide "View Settings" button when user is logged out by @bmomberger-bitovi in #262
• naming updates by @DavidNic11 in #261
• fix app key by @DavidNic11 in #263
• bitovi.tools by @DavidNic11 in #264

Status Reports for Jira

Overview

We made the following changes:

• We renamed the app Status Reports for Jira. This reflects Jira's trademark requirements and focuses more on what the app attempts to do - automate statue reporting for Jira.
• The plugin layout now removes the header, making the UI look much more seamless when the app is used as a Jira plugin

What's Changed

• TR-159: Previous name for a report is shown when editing the name for a subsequent report by @binaryberserker in #250
• A step forward towards improving the folder organization by @justinbmeyer in #251
• Poc/routing by @DavidNic11 in #254
• TR-105: Change the sidebar and top bar depending if the PLUGIN or the WEBAPP by @binaryberserker in #253
• dev docs by @DavidNic11 in #252
• Canjs folder refactor by @justinbmeyer in #256
• uses replace state on the slider by @justinbmeyer in #257
• starts enabling expanding children by @justinbmeyer in #258
• TR-162: Don't do O(n^2) over large data by @binaryberserker in #255
• Hiding the children in the appropriate way by @justinbmeyer in #259
• update verbiage by @DavidNic11 in #260
• [TR-137] Hide "View Settings" button when user is logged out by @bmomberger-bitovi in #262
• naming updates by @DavidNic11 in #261
• fix app key by @DavidNic11 in #263

Full Changelog: v0.8.2...v0.9.0

Saving Reports MVP

Saving Reports MVP

The saving reports MVP UI is now released. Users have the ability to create / update / copy / delete and rename reports.

What's Changed

• Tr 118 teams list by @DavidNic11 in #192
• adjusted starting to come together by @justinbmeyer in #196
• Tr 119 team all issues settings by @DavidNic11 in #195
• TR-23 Refactor rollup/dates by @binaryberserker in #194
• fixes by @DavidNic11 in #198
• fixing minor bugs in the team config by @justinbmeyer in #199
• loading indicator by @justinbmeyer in #200
• fixes #203 by properly including the parents key by @justinbmeyer in #204
• Tr 100 team issue configuration by @DavidNic11 in #206
• padding and divider changes by @DavidNic11 in #209
• add groups to select by @DavidNic11 in #210
• Tr 133 remove legacy configuration issue button by @DavidNic11 in #211
• Jira Typescript Conversion by @binaryberserker in #208
• remove issue ui by @DavidNic11 in #214
• this fixes the rollback makes the table grid tooltip a bit nicer by @justinbmeyer in #216
• Removing legacy velocity by @justinbmeyer in #217
• Tr 33 saving report mvp by @DavidNic11 in #213
• Staging report by @DavidNic11 in #218
• Removing legacy velocity by @justinbmeyer in #220
• TR-22: Refactor rollup/percent-complete by @binaryberserker in #221
• TR-139: Avoid "context limit exceeded" error by @binaryberserker in #222
• Fixes TR-147 by @justinbmeyer in #224
• Tr 33 saving report mvp by @DavidNic11 in #219
• TR-122: rolledup/work-status by @binaryberserker in #212
• TR-134: Prevent duplicate items from loading by @binaryberserker in #215
• TR-139: Avoid "context limit exceeded" error by @binaryberserker in #223
• small fix by @binaryberserker in #225
• remove logs by @DavidNic11 in #226
• TR-146: Remove the "Create new report" button from the "Saved Reports" page by @binaryberserker in #228
• add data syncs by @DavidNic11 in #227
• Tr 144 links in the saved reports dropdown by @DavidNic11 in #229
• Tr 140 create report should only show if there s a valid query by @DavidNic11 in #230
• account for empty childKeys by @DavidNic11 in #233
• remove reports by @DavidNic11 in #231
• Tr 149 empty epic in the future with timing shows complete by @DavidNic11 in #234
• TR-141: Don't reload after saving a report by @binaryberserker in #235
• TR-148: Select the report text when the modal opens by @binaryberserker in #236
• fixes TR-150 by @justinbmeyer in #240
• When grouping by parent, shows items with "no parent" by @justinbmeyer in #241
• TR-148: Select the report text when the modal opens by @binaryberserker in #238
• Tr 153 delete a saved report by @DavidNic11 in #245
• TR-152: Show the new name while saving by @binaryberserker in #246
• TR-148: Select the report text when the modal opens by @binaryberserker in #247
• Update/team list by @DavidNic11 in #243
• report style changes by @binaryberserker in #242
• docs by @DavidNic11 in #232
• fixes #239 and reverses the slider to see how it feels by @justinbmeyer in #248
• report fixes by @binaryberserker in #244
• fixes TR-160 by @justinbmeyer in #249

Full Changelog: v0.6.0...v0.8.2

v0.8.1

What's Changed

• Tr 118 teams list by @DavidNic11 in #192
• adjusted starting to come together by @justinbmeyer in #196
• Tr 119 team all issues settings by @DavidNic11 in #195
• TR-23 Refactor rollup/dates by @binaryberserker in #194
• fixes by @DavidNic11 in #198
• fixing minor bugs in the team config by @justinbmeyer in #199
• loading indicator by @justinbmeyer in #200
• fixes #203 by properly including the parents key by @justinbmeyer in #204
• Tr 100 team issue configuration by @DavidNic11 in #206
• padding and divider changes by @DavidNic11 in #209
• add groups to select by @DavidNic11 in #210
• Tr 133 remove legacy configuration issue button by @DavidNic11 in #211
• Jira Typescript Conversion by @binaryberserker in #208
• remove issue ui by @DavidNic11 in #214
• this fixes the rollback makes the table grid tooltip a bit nicer by @justinbmeyer in #216
• Removing legacy velocity by @justinbmeyer in #217
• Tr 33 saving report mvp by @DavidNic11 in #213
• Staging report by @DavidNic11 in #218
• Removing legacy velocity by @justinbmeyer in #220
• TR-22: Refactor rollup/percent-complete by @binaryberserker in #221
• TR-139: Avoid "context limit exceeded" error by @binaryberserker in #222
• Fixes TR-147 by @justinbmeyer in #224
• Tr 33 saving report mvp by @DavidNic11 in #219
• TR-122: rolledup/work-status by @binaryberserker in #212
• TR-134: Prevent duplicate items from loading by @binaryberserker in #215
• TR-139: Avoid "context limit exceeded" error by @binaryberserker in #223
• small fix by @binaryberserker in #225
• remove logs by @DavidNic11 in #226
• TR-146: Remove the "Create new report" button from the "Saved Reports" page by @binaryberserker in #228

Full Changelog: v0.6.0...v0.8.1

Team-Issue Configuration and Saving Reports MVP

What's Changed

• Tr 118 teams list by @DavidNic11 in #192
• adjusted starting to come together by @justinbmeyer in #196
• Tr 119 team all issues settings by @DavidNic11 in #195
• TR-23 Refactor rollup/dates by @binaryberserker in #194
• fixes by @DavidNic11 in #198
• fixing minor bugs in the team config by @justinbmeyer in #199
• loading indicator by @justinbmeyer in #200
• fixes #203 by properly including the parents key by @justinbmeyer in #204
• Tr 100 team issue configuration by @DavidNic11 in #206
• padding and divider changes by @DavidNic11 in #209
• add groups to select by @DavidNic11 in #210
• Tr 133 remove legacy configuration issue button by @DavidNic11 in #211
• Jira Typescript Conversion by @binaryberserker in #208
• remove issue ui by @DavidNic11 in #214
• this fixes the rollback makes the table grid tooltip a bit nicer by @justinbmeyer in #216
• Removing legacy velocity by @justinbmeyer in #217
• Tr 33 saving report mvp by @DavidNic11 in #213
• Staging report by @DavidNic11 in #218
• Removing legacy velocity by @justinbmeyer in #220

Full Changelog: v0.6.0...v0.8.0

Team Configuration and Spreading Estimates

This release brings:

• Teams Configuration - Configuration settings specific each team
• Spreading Estimates - Instead of using primarily dates to determine how much work is complete, use the estimate spread across the dates to determine how much work is complete

Teams Configuration

Different teams might use different settings for dates, estimates, etc. You can now configure these in the Teams global settings sidebar menu:

Clicking the Teams button will show a list of teams that can be configured individually:

NOTE: A team is either the team field value or the project key (if there is no team)

Clicking a Team lets you configure that team's settings. The following shows the BUY team's configuration:

Notice that the team is inheriting all it's values from the Default Settings. To change this, click CUSTOMIZE and then change the value. For example, the following sets the BUY team's velocity to 25:

Spreading Estimates

The percent complete rollup would use the timing of issues to determine how much work has been completed. For example, an issue that had a start and due date 20 business days apart would always be considered as 20 days of work.

This doesn't make sense for work that is spread out over time. For example, lets say some work is 5 days of work, but is going to be done over 20 days. You'd want to spread that 5 days of work over 20 days. This is exactly what the new Spread effort toggle does ... turning it on:

• spreads your estimate across the dates to determine how much work has been done, and
• uses the estimate as the total amount of work

Let's see an example!

The following 3 epics use a Days Estimate field to track the amount of work they have to do. However, they all share the same start and due dates:

Each epic's start and due dates are 20 days apart. If we look at the base behavior of the Baseline Report, it will show each of these epics as needing 20 days of work:

However, if we configure to spread the estimate across time:

Now you can see the total work is calculated from the estimate. The percentage of work complete is still using the dates. But the percentage uses the estimated work for calculating completed and remaining work totals.

What's Changed

• Tr 118 teams list by @DavidNic11 in #192
• adjusted starting to come together by @justinbmeyer in #196
• Tr 119 team all issues settings by @DavidNic11 in #195
• TR-23 Refactor rollup/dates by @binaryberserker in #194
• fixes by @DavidNic11 in #198
• fixing minor bugs in the team config by @justinbmeyer in #199
• loading indicator by @justinbmeyer in #200

Full Changelog: v0.6.0...v0.7.0