Copy or Move worklogs entered by users from one issue to another linked issue
Copy or Move worklogs entered by users from one issue to another linked issue
Copy or Move worklogs entered by users from one issue to another linked issue
Sync Worklog
Move Worklog
Link Types
Worklog sync gives you the ability to move or copy worklogs entered on issues to other linked issues on a Jira instance.
You can configure if worklogs will be copied or moved. A comment will be left both on the issue where the worklog was entered and the issue where the worklog is copied/moved to.
You can configure which link type and the direction of the link to be moved/copied.
More details
Worklog sync gives you the ability to move or copy worklogs entered on issues to other linked issues on a Jira instance.
You can configure which link type and the direction of the link to be moved/copied.
You can configure if worklogs will be copied or moved.
A comment will be left both on the issue where the worklog was entered and the issue where the worklog is copied/moved to.
Jira 6.x version is also compatible. Please check Version History page.
Reviews for cloud
(7)Sign in to write a review
Hi Jan,
Thank you for your interest in our plugin.
JIRA and TempoTimesheets keep the worklogs in the same JIRA data structure so we expect no difference in behavior or worklog sync if the worklog is entered through plain JIRA screens or TEMPO Timesheets.
Accounts field is specific to TT and current is not supported. Having the Account field also synced might be a good feature to have and I will pass this to the product manager as a feature request.
Lastly, we have another plugin named Field Sync. It is capable of syncing many types of field values between JIRA issues. You might consider using that plugin to sync the account field.
EmreT
Reviews for server
(7)Sign in to write a reviewHi Jan,
Thank you for your interest in our plugin.
JIRA and TempoTimesheets keep the worklogs in the same JIRA data structure so we expect no difference in behavior or worklog sync if the worklog is entered through plain JIRA screens or TEMPO Timesheets.
Accounts field is specific to TT and current is not supported. Having the Account field also synced might be a good feature to have and I will pass this to the product manager as a feature request.
Lastly, we have another plugin named Field Sync. It is capable of syncing many types of field values between JIRA issues. You might consider using that plugin to sync the account field.
EmreT
Reviews for Data Center
(7)Sign in to write a reviewHi Jan,
Thank you for your interest in our plugin.
JIRA and TempoTimesheets keep the worklogs in the same JIRA data structure so we expect no difference in behavior or worklog sync if the worklog is entered through plain JIRA screens or TEMPO Timesheets.
Accounts field is specific to TT and current is not supported. Having the Account field also synced might be a good feature to have and I will pass this to the product manager as a feature request.
Lastly, we have another plugin named Field Sync. It is capable of syncing many types of field values between JIRA issues. You might consider using that plugin to sync the account field.
EmreT
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$10 | 25 users$40 | 50 users$75 | 100 users$150 | 250 users$225 | 500 & upAdditional pricing details |
Pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 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 Atlassian 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 Atlassian product. For Jira 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 (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira 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.
- Can I install this app in a Data Center product?
This app does not have a a Data Center approved version. Only apps meeting a set of performance requirements for large, clustered environments are approved for Data Center.
However, while server apps are built for single-server deployments, many customers successfully install them in Data Center products. If you're using a Data Center product, Atlassian recommends you contact the vendor to determine compatibility at scale.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app does not have a Data Center approved version, you should purchase a Server license if you decide to install this app in a Data Center product.
- Do you offer academic, community, or open-source licenses for server apps?
For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are available for server apps. Learn more about community and open source licenses.
- Can I extend my free trial?
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 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.
OBSS is a Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 1.6.7.j7 • Jira Server 7.0.0 - 7.12.3 • Released 2018-09-23
Summary
Maintenance release
Details
Bugfixes
- Settings cannot be saved when using PostgreSQL
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Worklog Sync via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Worklog Sync. You're prompted to log into MyAtlassian. Worklog Sync begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- 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 Worklog Sync versions compatible with your instance, you can look through our version history page.
Similar apps
