Page tree
Skip to end of metadata
Go to start of metadata

I've uninstalled Time in Status plugin but a custom field named Time in Status remains on my system

  • Time in Status by OBSS does not introduce any custom fields or custom field types to your system. Even tough the custom field name is similar, it must belong to another plugin. Some other plugins are known to create custom fields with similar names. For example, Jira Suite Utilities is known to have such a field.

I see some values as 0.00 and some values as a dash ("-") on my screen. What are those?

  • When report values are displayed on screen in Days, Hours or Minutes; the decimal values displayed in the report are rounded down to two decimal points, for readibility on screen. The calculation of duration of a very short visit to a status (for example a few seconds) results in a value that is very close to zero and when rounded to two decimal points, the value actually becomes 0.00 . 
    Such very short durations are intentionally left to be displayed as 0.00 because they are too small to be displayed above 0.00 but we want them to be distinguishable from non-visited statuses (which are displayed as a dash ("-") instead of a duration).
    If you change your view format to "seconds", you will see that those 0.00 values will show small durations. You can also export your data to a file. File exports include durations in full precision.

The values I see on screen and the values in the export file do not match. The export file contains too many decimal points. Why is that? 

  • When report values are displayed on screen in Days, Hours or Minutes; the decimal values displayed in the report are rounded down to two decimal points, for readibility on screen. 
    On the other hand, users export data to a file to perform further calculations so we export data with maximum precision.
    Almost all spreadsheet applications allow you to format the values you see in your spreadsheet. You can use your spreadsheet applications's functions to display the values in any way you need.

I can't install Time in Status on my Jira Cloud instance for evaluation. The install process starts but fails after a few minutes. The app is automatically uninstalled.

  • Atlassian does not allow starting new evaluations if there is a billing issue on your instance. Unfortunately Jira does not show an error message to the user that includes a good guiding explanation for this. Please make sure that you don't have late payments, etc.

I am getting ""Time in Status needs "Browse Users and Groups" global permission to execute this functionality" warning.

  • This is a rare warning that occurs when you change Time in Status Access Settings to grant app access to only specific user groups (rather than everyone) and you do not grant Browse Users and Groups Jira global permission to Time in Status.
    All apps operate with a user account on your Jira Cloud instance. Normally these accounts are hidden from you by Jira (since there is no point for you to see them) but the accounts are there anyway.
    These accounts are (by default) members of user groups that are marked with Default Access Group and those user groups (once again by default) have Browse Users and Groups global permission.

    Time in Status in particular needs Browse Users and Groups global permission to execute its full functionality.
    You will see the aforementioned warning if you remove those user groups, that contain Time in Status app user, from Browse Users and Groups global permission and set Time in Status Access Settings to allow only particular user groups.

    There is no way for you in Jira Cloud to add app user accounts to any other user groups since those accounts are not visible to you but this warning will most likely be gone if you grant Browse Users and Groups global permission to user groups marked with Default Access Group.

I've migrated my Jira data from one Jira Cloud instance to another. Now I can't use Time in Status.

  • The backup and restore routine on Atlassian Cloud has some known bugs and damages the app user during a backup & restore operation. The recommended way to resolve this issue is to open a support request to Atlassian through . Atlassian technical people will fix the damaged app user in the database. A simple uninstall/reinstall of the app will resolve your issue.

    We will be happy to assist you in this process. If you need help with this, open a support ticket to us through . Our support team will give you contact details to pass on to Atlassian Support so we will provide the necessary technical details when needed.

How can I get support about Time in Status

  • No labels