1,984
Customers have installed this add-on in at least 1,984 active instances.
1,984
Customers have installed this add-on in at least 1,984 active instances.
    by SoyatecAtlassian Verified
    Soyatec is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for JIRA Cloud, JIRA Server 7.0.0 - 7.2.6 and more versions
    Versions available for JIRA Server 4.2 - 6.4.14
    Supported
    Soyatec supports this add-on.

    Get support

    Supported
    Soyatec supports this add-on.

    Get support

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

    Project Planning and Tracking in Gantt Chart like MS Project - Free License is avaliable

    Project Planning and Tracking in Gantt Chart like MS Project - Free License is avaliable

    Project Management

    Project Plan

    Project Tracking

    An Enterprise Project Management Solution for JIRA,

    JIRA Standard Compliant JIRA Agile Compatible Microsoft Project Interoperable

    It extends JIRA solution by providing comprehensive and powerful planning capabilities to accurately plan and centrally manage your projects.

    Enables all team members to collaborate together directly in a common system. The project managers can quickly pinpoint variations in actual project performance from intended project goals.

    Project Management

    Project Plan

    Project Tracking

    An Enterprise Project Management Solution for JIRA,

    JIRA Standard Compliant JIRA Agile Compatible Microsoft Project Interoperable

    It extends JIRA solution by providing comprehensive and powerful planning capabilities to accurately plan and centrally manage your projects.

    Enables all team members to collaborate together directly in a common system. The project managers can quickly pinpoint variations in actual project performance from intended project goals.

    More details

    The basic features are FREE for everyone and forever only with self-hosted JIRA. It is not available for JIRA Cloud. The Free license can be requested via "License Management" under the menu "Gantt chart".

    The detail information can be found on the project web page: http://www.jiraproject.com

    More details

    The basic features are FREE for everyone and forever only with self-hosted JIRA. It is not available for JIRA Cloud. The Free license can be requested via "License Management" under the menu "Gantt chart".

    The detail information can be found on the project web page: http://www.jiraproject.com

    User reviews

    (145)
    Sign in to write a review »
    by Alexey Gnoevoy on 2016-11-16
    OK
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Chris Morgan on 2016-10-31
    Had errors when going through the install process, not sure if that has any impact on functionality but it doesn't give a warm and fuzzy feeling about this add-on.
    Was this review helpful?YesNo
    by Rodrigo Goncalves on 2016-10-28
    Extremely buggy, doesn't accept one task be the predecessor of 2 different tasks. Seems to be the only add on working, but has to be patient. I wouldn't recommend, maybe a next version would be better.
    Was this review helpful?YesNo
    by George Polchin on 2016-10-03
    Note: If you try the free trial and then click "Paid upgrade" there is no confirmation! It will install it immediately (and start charging you...) I immediately did "unsubscribe" but now am not sure whether I got charged.
    Was this review helpful?YesNo
    by Abdelazim Mohamed on 2016-09-06
    alot of errors occurred like this one: java.lang.RuntimeException: java.lang.RuntimeException: [ErrorCollection{status=400, errors={}, errorMessages=[Field 'assignee' does not exist or you do not have permission to view it., Field 'duedate' does not exist or you do not have permission to view it.]}]:(assignee = "admin") AND ((duedate >= '2016-08-09') OR (duedate is null)) at com.soyatec.jira.resourcetracking.ResourceTrackingContentProvider.fetchGanttData(ResourceTrackingContentProvider.java:119) at com.soyatec.jira.resourceplanning.ResourcePlanningAction.generateGanttchartData(ResourcePlanningAction.java:22) at com.soyatec.jira.actions.GanttChartContextAction.refresh(GanttChartContextAction.java:68) at com.soyatec.jira.plugins.service.GanttResource.loadChart(GanttResource.java:130) at sun.reflect.GeneratedMethodAccessor70.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339) at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.soyatec.jira.interceptor.AbstractFilter.doFilter(AbstractFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1024) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1686) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at com.soyatec.jira.resourcetracking.ResourceTrackingContentProvider.fetchGanttData(ResourceTrackingContentProvider.java:164) at com.soyatec.jira.resourceplanning.ResourcePlanningAction.generateGanttchartData(ResourcePlanningAction.java:22) at com.soyatec.jira.actions.GanttChartContextAction.refresh(GanttChartContextAction.java:68) at com.soyatec.jira.plugins.service.GanttResource.loadChart(GanttResource.java:130) at sun.reflect.GeneratedMethodAccessor70.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339) at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.soyatec.jira.interceptor.AbstractFilter.doFilter(AbstractFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1024) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1686) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) It seems there is a problem of JIRA permission configuration for Gantt Chart Project. Please contact the support of JIRA or Soyatec.
    Was this review helpful?YesNo

    Pricing

    Pricing details are loading…

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does cloud add-on pricing work?

    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, your pricing tier for host products and add-ons is automatically adjusted (as necessary) based on the number of users in your instance.

    If you've opted for annual billing for your host product, add-ons are also billed annually. Annual subscriptions for this add-on include a discount (12 months for the price of 10).

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

    The cloud add-on tier is set automatically based on the maximum tier of the licensed JIRA applications on your instance. For example, if you have JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, your add-on tier is 50 users.

    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 cloud add-ons, you cannot extend your free evaluation period. All cloud add-ons 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 add-on.

    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

    Soyatec is Atlassian Verified. Verified add-on vendors demonstrate high quality, reliability, and business traction. Learn more

    Soyatec supports GanttChart Project for JIRA - Enterprise. You can visit the support site to get help.

    Get support

    Soyatec is Atlassian Verified. Verified add-on vendors demonstrate high quality, reliability, and business traction. Learn more

    Soyatec supports GanttChart Project for JIRA - Enterprise. You can visit the support site to get help.

    Get support

    Versions

    JIRA Cloud Released 2016-03-25

    Summary

    Support of MS Porject 2016 and Improvement of EPIC management

    Details

    Bug

    Improvement

    New Feature

    Versions

    Version 3.6.21 JIRA Server 7.0.0 - 7.2.6 Released 2016-06-12

    Summary

    Add the filters on EPIC and Sprint

    Details

    Bug

    • [JRAGANTT-394] - The duration comes back to original estimation when the estimate becomes 0
    • [JRAGANTT-395] - Resolution Date isn't used as End time all time.
    • [JRAGANTT-396] - Reset the state of issues after the deletion of dependency

    Improvement

    • [JRAGANTT-391] - The AutoScheduler uses the current time to schedule the AutoScheduled Issues.

    New Feature

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

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Find new add-ons screen loads.
    3. Locate GanttChart Project for JIRA - Enterprise.
    4. Click Free trial to download and install your add-on.
    5. You're all set! Click Close in the Installed and ready to go dialog.

    Similar add-ons