11
Customers have installed this add-on in at least 11 active instances.
    by OBSSfor JIRA Server 7.0.0 - 7.1.10 and more versions
    Versions available for JIRA Server 5.2 - 6.4.14
    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

    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 noth 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 noth 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.

    User reviews

    (6)
    Sign in to write a review »
    by Jan Prokeš on 2016-04-26
    Hi, it works as it should for Jira Worklogs, but it does when Tempo timesheets is used. Is there any plan for extending addon for Tempo timesheets? At least Account field? Thank you.
    Was this review helpful?YesNo

    OBSS

    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

    by Sergio Silva on 2015-03-13
    Hi! When worklog sync will be Data Center certified?
    Was this review helpful?YesNo

    OBSS

    Hi Sergio, We have updated plugin and it is now compatible with 6.3. JIRA DataCenter compatibility is something we are considering to implement in medium term. (3-6 Months) Best Regards OBSS Atlassian Team
    by Artsiom Siamenchykau on 2014-02-14
    it's exactly what we were looking for. thx!
    Was this review helpful?YesNo

    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 tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications 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 application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free 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 application, 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

    Support

    OBSS supports Worklog Sync. You can visit the support site to get help.

    Get support

    Versions

    Version 1.6.2 JIRA Server 7.0.0 - 7.1.10 Released 2015-11-06

    Summary

    JIRA 7 Support

    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 Worklog Sync 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 Worklog Sync. You're prompted to log into MyAtlassian. Worklog Sync 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 Worklog Sync versions compatible with your instance, you can look through our version history page.

    Similar add-ons