"Automatic" mode

When work is over, press "Stop timer" button to log automatically calculated work time.

Track time on the go in Jira and Jira Software.

In this mode, timer starts when issue goes to "In Progress" (or other "active" status). When issue is moved to Done, Closed, Open, etc. work time is logged automatically.

More details

Automated Log Work app allows tracking work time precisely and seamlessly in Jira.

It helps when:

You have to log work against Jira issues.

You find it difficult to remember when you started working on an issue.

You are fatigued by manually calculating how long you have worked on an issue.

Automated Log Work offers "Manual" and "Automatic" modes.

In "Manual" mode, press "Start Timer" button on the issue page to start the timer. When work is over, press "Stop Timer" button to stop the timer and save the automatically calculated worked time value.

Privacy and security

Privacy policy

Security

This vendor has not completed the security self-assessment.

Cloud app vendors are encouraged to complete a yearly self-assessment of their data security practices. This information is self-reported by vendors, and Atlassian is not responsible for the security or integrity of this app.

Resources

Integration details

Automated Log Work for Jira integrates with your Atlassian product. This remote service can:

Act on a user's behalf, even when the user is offline

Write data to the host application

Read data from the host application

More details

Automated Log Work app allows tracking work time precisely and seamlessly in Jira.

It helps when:

You have to log work against Jira issues.

You find it difficult to remember when you started working on an issue.

You are fatigued by manually calculating how long you have worked on an issue.

Automated Log Work offers "Manual" and "Automatic" modes.

In "Manual" mode, press "Start Timer" button on the issue page to start the timer. When work is over, press "Stop Timer" button to stop the timer and save the automatically calculated worked time value.

The plugin posts updates to Activity Stream that are visible for everyone in the system regardless of permissions (with user names and issue keys - even if a user doesn't have Browse Users global permission).
What is more disappointing, all the data published in the activity stream remains visible even after uninstalling the plugin.
For me: unreliable and not worth any money.

When comes to Browse Users permission in JIRA, it is used in user selection boxes like "mention" in comments. It does not block user without permission to see other users profile, links or names. Therefore you can reproduce the problem you mentioned without our add-on installed, e.g. transition an issue or log work against an issue. The user w/o Browse Users permission will still see in activity stream who logged time.

The other thing is that activity stream does not hide entries if their author (user or plugin) disappears from the system. Again, you can reproduce that without our add-on installed, e.g. log work against an issue and next delete the user who logged work. The other users will still see a corresponding entry in activity stream, even though the user who logged work is no longer available in JIRA.

Overall, these two problems you mentioned are JIRA specific - this is how JIRA works.

Your main requirement for our add-on is to disable activity stream integration. That feature is on our roadmap and should appear in one of the oncoming versions.

You can contact us directly at support@gebsun.com if further clarification is needed.

The plugin posts updates to Activity Stream that are visible for everyone in the system regardless of permissions (with user names and issue keys - even if a user doesn't have Browse Users global permission).
What is more disappointing, all the data published in the activity stream remains visible even after uninstalling the plugin.
For me: unreliable and not worth any money.

When comes to Browse Users permission in JIRA, it is used in user selection boxes like "mention" in comments. It does not block user without permission to see other users profile, links or names. Therefore you can reproduce the problem you mentioned without our add-on installed, e.g. transition an issue or log work against an issue. The user w/o Browse Users permission will still see in activity stream who logged time.

The other thing is that activity stream does not hide entries if their author (user or plugin) disappears from the system. Again, you can reproduce that without our add-on installed, e.g. log work against an issue and next delete the user who logged work. The other users will still see a corresponding entry in activity stream, even though the user who logged work is no longer available in JIRA.

Overall, these two problems you mentioned are JIRA specific - this is how JIRA works.

Your main requirement for our add-on is to disable activity stream integration. That feature is on our roadmap and should appear in one of the oncoming versions.

You can contact us directly at support@gebsun.com if further clarification is needed.

The plugin posts updates to Activity Stream that are visible for everyone in the system regardless of permissions (with user names and issue keys - even if a user doesn't have Browse Users global permission).
What is more disappointing, all the data published in the activity stream remains visible even after uninstalling the plugin.
For me: unreliable and not worth any money.

When comes to Browse Users permission in JIRA, it is used in user selection boxes like "mention" in comments. It does not block user without permission to see other users profile, links or names. Therefore you can reproduce the problem you mentioned without our add-on installed, e.g. transition an issue or log work against an issue. The user w/o Browse Users permission will still see in activity stream who logged time.

The other thing is that activity stream does not hide entries if their author (user or plugin) disappears from the system. Again, you can reproduce that without our add-on installed, e.g. log work against an issue and next delete the user who logged work. The other users will still see a corresponding entry in activity stream, even though the user who logged work is no longer available in JIRA.

Overall, these two problems you mentioned are JIRA specific - this is how JIRA works.

Your main requirement for our add-on is to disable activity stream integration. That feature is on our roadmap and should appear in one of the oncoming versions.

You can contact us directly at support@gebsun.com if further clarification is needed.

Pricing FAQ

Cloud pricing is subscription based. You are eligible for support and automatic version updates as long as your subscription is active.

When your subscription renews each month, you are automatically billed for host products and apps based on the number of users in your instance.

If app 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 cloud pricing?

Apps are billed based on the number of users in your host product. Jira Cloud apps are priced based on the maximum users of the Jira products on your instance. For example, if you have Jira Software (50 users) and Jira Service Desk (10 agents) on the same instance, you pay the 50-user price for apps.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for licensing across maximum users still apply.

The pricing structure for cloud products and apps is as follows:

Monthly subscriptions with up to 10 host product users are billed at a flat rate price.

Monthly subscriptions with more than 10 users are billed per user, starting at the first user.

Monthly subscriptions with more than 100 users are billed per user. The table above provides example pricing at various user levels.

If per-user pricing is not yet available for this app, please contact the vendor for further information.

If you've opted for annual billing for your host product, apps are also billed annually at a discount (12 months for the price of 10).

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

Academic, community and open source licenses are not available for cloud apps.

Can I extend my free trial?

For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.

Pricing FAQ

How does server app pricing work?

Server products and apps 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 app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

If app 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?

Apps are billed based on the number of users in your host product. For Jira Server 7.0 or later, the app 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 apps. For versions of Jira Server prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

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

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

For server apps, you can extend your app 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 app listing in UPM from your Atlassian host product, and you're all set.

How can I buy apps 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 app pricing is no longer available. You have two options for app purchasing:

Purchase the app at the non-legacy Unlimited (10000+ users) tier.

Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.