460
Customers have installed this add-on in at least 460 active instances.
    by OBSSfor JIRA Server 6.1 - 7.3.8 and more versions
    Versions available for JIRA Server 6.0 - 6.0.8
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    OBSS supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    Report how much time each issue spent on each status or on each assignee

    Report how much time each issue spent on each status or on each assignee

    Report Types

    Advanced Report & Time Configuration

    Export your report flawlessly

    Report the amount of time each issue has spent on each status or on each assignee. Create reports for issues of a user, issues in a project or issues in a filter.

    Select time period for reports, down to minute resolution. Get reports grouped by Issue or Issue Type. Create reports based on 7/24 calendar or business calendar.

    Easily export the data to excel format or to print version format.

    More details

    Time In Status allows you to create reports on issues that shows how much time each issue spent on each status or on each assignee. This report can be used to identify bottlenecks, to measure performance or even for SLA targets.

    You can report on issues of a user, issues in a project or, for maximum flexibility, issues in a saved filter. You can set date intervals for the report down to minute resolution. Also can include system or custom fields in the report output as columns.

    Report can be configured to report on statuses of assignees. That means you can see how much time each issue spent on each status or each assignee.

    Creating reports based on 7/24 calendar or business hours is supported. Also, exporting report data to Excel is available.

    User reviews

    (21)
    Sign in to write a review
    by Saravanan Rajaram on 2017-06-14
    plugin gives me the time in status but have two challenges, 1.We have two teams one working in EST hours and one working in IST. Which means we need to configure two slots of business hours but for the business hours config whereas the current option is to configure just one 2. Also since one team works in IST hours their work time starts @ 9 AM IST which happens to be Sunday night EST hours which will be marked as non business hours. So any work picked may not be counted. I believe this could be common scenario wherever offshoring is followed and thought you may have already seen this. Any solutions ??
    Was this review helpful?YesNo
    OBSS

    Hi Saravanan,

    Thank you for reaching us.

    "Having multiple business hours definitions" is a sound request for customers working with teams in multiple time zones or in multiple shifts. Even so, we have seen this request only once in the past. It is in our backlog and we are watcing the request if it gains more traction.

    Your use case is very valuable for us since it will give us more insight into the actual need. Please contact us through plugin@obss.com.tr or servicedesk.obss.com.tr so we can discuss the matter further.

    OBSS Atlassian Team

    by Elie Nasser on 2017-04-27
    I was happy when I found Time In Status add-on, but there was few things I needed to see improved to make full use of its potential. It took >7 months to provide all the features/improvements i requested, but the end result is good. Thank you for delivering what I was asking; the plugin is now much more useful with those improvements.
    Was this review helpful?YesNo
    OBSS

    Hello Elie,

    I am glad to hear that we could help you with our support.

    Our current support process gives highest priority to bugs on existing features. Anyone who gets an error or cannot use the product due to some mulfunction gets the highest priority. The target is to fix the product as soon as possible so customer can start using it as soon as possible. I believe we are pretty much successful with this target.

    On the other hand any improvement or new feature requests are escalated to product backlog and is reviewed by the development team in two weeks most of the time. The customer is informed about our first evaluation result, whether the intention about the request is positive or negative. If it is a clear reject, we do not want to give false hopes to the customer so say it up front. If it is positive, the item stays in the backlog and evaluated further.

    The important thing is, keeping the item in the backlog does not guarantee when or even if the feature is going to be implemented. Any new request, no matter how small it seems, gets into our existing development roadmap and might not be that easy to develop.

    Your improvement requests were also evaluated by the team and our first evaluation is positive. We informed you about that. We also believe, as you do, that those features would add value to our products. Nevertheless, due to existing plans and resource assignments we cannot start developing them today. We will keep them in the backlog and will try to put into our roadmap in the future.

    Thank you once more for your interest in our plugin.

    Emre TOPTANCI

    OBSS Atlassian Team Lead

    by Mark Rowlands on 2017-03-20
    Hello, Like some others here I would like to see a cloud version of this add-on. Any plans for this? Thanks
    Was this review helpful?YesNo
    OBSS

    Hi Mark,

    I am glad to inform you that we have the final management decision to build a cloud version of Time in Status. Development started a few months ago and still going.

    We will do our best to release the cloud version as soon as possible.

    OBSS

    by Giampietro Calabrese on 2017-01-24
    Hello, any news about Cloud version? Thank you
    Was this review helpful?YesNo
    OBSS

    Hi,

    I am glad to inform you that we have the final management decision to build a cloud version of Time in Status. Development started a few months ago and still going.

    We will do our best to release the cloud version as soon as possible.

    OBSS

    by Mustaq on 2016-08-11
    I have tried many plugins to get a report of how much time a set of JIRA tasks (JIRA saved filter) spend in a particular status. This tool beat out all other tools for my use. As a QA manager, this tool helps me study time in status for JIRA tasks "waiting to be tested" as well as how much time tasks spend "in QA". One of the best option in this plugin is ability configure company specific business hours and holidays. Reports can still be generated based on business days or 24/7 time/days counting. The advanced option allows for selecting for saved JQL queries. Another great feature is, option to select only the status that need to be included in the report and unselect anything that is not needed. Export to Excel option is great as well. For me, the most useful sections are the "Hour Based Report" and the "Hour Based Average Report". Functionally, this plug works. However, it could use some speed improvements, better UI and layout.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    OBSS

    Hi Mustaq,

    Thank you very much for the kind review. Your satisfaction is most important to us.

    Speed is one of our top concerns about the plugin. Since the plugin has to go through not only all issues but also through each issue's history, it is a quite I/O intensive operation on the server. We made some optimizations to improve the user experience and execution speed with versions 2.0 and 2.1. You can bet we will continue working on it.

    Best Regards,

    OBSS Atlassian Team

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing?

    Add-ons are billed based on the number of users in your host product. For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA products on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for add-ons. For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server add-ons are always free for community and open-source licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the add-on listing in UPM from your Atlassian host product, and you're all set.

    How can I buy add-ons for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more

    OBSS provides support for this add-on.

    Vendor support resources

    Documentation

    Find out how this add-on works.

    Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this add-on.

    Versions

    Version 2.6.3-488 JIRA Server 6.1 - 7.3.8 Released 2017-06-21

    Summary

    Maintenance Release

    Details

    [APDTIS-634] - Excel export should give unrounded values

    Installation

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Time in Status via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Time in Status. You're prompted to log into MyAtlassian. Time in Status begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older Time in Status versions compatible with your instance, you can look through our version history page.

    Similar add-ons