BigGantt - Gantt Chart for Jira

they advertise it as if it contains the Resource module but it is not true, it only offers the overview module and the gantt module.

• 

  Appfire

  Hi Marta,

  We're sorry the app fell short of what you expected. Let us lay out what BigGantt actually ships and where resource tracking sits.

  The Overview and Gantt modules are the full lineup, and resource capacity is handled inside the Gantt module by the Resources panel: per-person and per-team workload against capacity, shown in hours, man-days, percent, or story points. The stand-alone Resources module is part of BigPicture, not BigGantt. I'll flag your note to the team so the listing spells that out better.

  If the panel doesn't cover what you planned to do, or BigPicture would be the better fit, we're happy to sort that out with you at our support portal.

  Best regards,

  Paweł Customer Success Team | Appfire

BigGantt makes no sense as a visualization tool. When you remove a project from the Gantt view, it actually deletes the corresponding Jira issues from your workspace. This is completely unacceptable — a Gantt chart should never destroy data. And to make things worse, there’s no trash bin or recovery option, so the deleted issues are gone for good.

• 

  Appfire

  Hi Brahim,

  Losing Jira issues you expected to keep is about the worst surprise a planning tool can give you, and I understand why this earned one star.

  What happened: in BigGantt, Delete removes the task and, when that task is synchronized with a Jira issue, the issue itself. This is documented in Delete task, and it cannot be undone from the app. The non-destructive way to take things off the Gantt is excluding them from scope (Box configuration, then Tasks, then Scope definition), which hides them from the view and leaves every issue in Jira untouched.

  That distinction clearly did not protect you here, and I'm passing that to the product team.

  Please contact us at our support portal; depending on your instance and backups, your Jira admin may still have recovery paths, and we can help you check.

  Best regards,

  Paweł Customer Success Team | Appfire

After reporting a blocking defect to support (SUPPORT-252131), nothing was done for 24 hours. Unless you start pinging them, they don’t seem to have any intention of fixing issues at all.

• 

  Appfire

  Hi Rodion,

  Thank you for sharing this feedback, we’d like to clarify the current status for everyone following the thread.

  In the referenced case (SUPPORT-252131), our team identified a bug impacting live synchronization from Jira to BigGantt (Jira → BigGantt direction). The fix was completed after this review was posted and is now ready for release. It will be included in the upcoming production version.

  In the meantime, the affected instance has been moved to an isolated server environment to ensure synchronization remains stable until the official release is deployed.

  If anyone experiences similar sync behavior, please contact us directly via our support portal so we can securely collect diagnostics and respond promptly.

  We appreciate your feedback, reliability and transparency are very important to us, and we’ll continue improving both.

  Warm regards,

  Paweł Customer Success Team | Appfire

Everything is great, but due to a few unresolvable settings, I had to stop using it: 1. The minimum task duration in days = 1, which means even a 2-hour task is treated as a full-day task. If you link another task with an End-to-Start dependency, it can’t be placed on the same day with a hard link. You can work around this (for example, by setting a -1 day offset in the dependency), but doing it manually is inconvenient when planning a large number of tasks. 2. It’s not possible to set a soft link as the default.

• 

  Appfire

  Hi Андрей,

  Thank you for your feedback and for highlighting the aspects of the app you enjoyed! We truly appreciate you sharing these specific details about your workflow. It sounds like you are looking for more granular control over task scheduling and dependencies to better reflect short-term activities within your Confluence tables.

  We understand how frustrating it is when default settings (like the minimum duration or dependency types) don't align with the precision your project requires, especially when dealing with a high volume of tasks. Our goal is to make planning seamless, and having to resort to manual offsets or workarounds definitely adds unnecessary friction to your process.

  We would like to investigate if there are upcoming updates to our Gantt or scheduling features that address these logic constraints. Please reach out to us at our support portal so we can look into your current configuration and see if we can provide a more automated solution for you. If we can help resolve these blockers, we’d love the chance to welcome you back to the app.

  Kind Regards,

  Paweł Customer Success Team | Appfire

• 

  Appfire

  Hi Sergio,

  It looks like something didn’t go quite right with BigGantt, and we’d really appreciate the chance to understand what happened. If you're open to it, could you share a bit more about your experience?

  Your feedback helps us improve, and we’d love to make sure BigGantt works the way you need it to. You can reach us anytime at our support portal: https://apps.appf.re/support. We're here and happy to help.

  Warm regards,

  Paweł Customer Success Team | Appfire