[XenCustomize] Project Tracker [Paid] 2.3.1

[Veer]

Veer submitted a new resource:

[XenCustomize] Project Tracker - Track your projects with milestone-based progress, roadmap items, work logs, timelines, and more!

XenCustomize Project Tracker for XenForo 2!​

A beautiful, fully-featured project management & public roadmap system — built right inside your XenForo community.

Stop juggling spreadsheets and scattered forum threads. Project Tracker brings milestone-based...

Read more about this resource...

 

[Alpha1]

@pegasus does this have the functionality you need to migrate your vbulletin Project Tools to XenForo?

VaultWiki - Wiki for Forum Communities - Support

VaultWiki, Wiki addon for vBulletin forums. Licensing and support site.

www.vaultwiki.org

 

[pegasus]

This seems really promising as a replacement for vBulletin Project Tools. However, there is one major issue that's been holding us back from converting our project tools installation to a XenForo solution. For XenCustomize, I see:

Per-project visibility: Visible or Private

Can these visibility options be changed individually per item within a project? And per reply within an item?

In the installation we're looking to migrate, we have situations like this:
- Public Project
--- Public thread
--- Private thread
--- Public thread
------ Public reply
------ Private reply
------ Private reply
------ Public reply

Private threads/replies can be viewed by the thread owner, the post owner, and mods/admins. I believe it's a separate usergroup permission (can view others' private posts). This is different and separate from moderation status, because the post owner can change the visibility themselves.

We have hundreds of individual threads that users have marked private within public projects, and hundreds of individual posts marked private that are in public threads. If this system can accommodate this without massive changes, we'll take a look.

Also, it isn't clear from the description -- are items posted within projects able to use XenForo's custom thread fields? Or does it at least have its own ability to create custom fields?

 

[Veer]

@Alpha1 @pegasus
Hi there, and thank you for the thoughtful questions. You are asking exactly the right things before planning a migration.

At the moment, this addon does not support mixed visibility (for example: a public project containing some private individual items/log entries).

Current behavior is:

1. Visibility is only at the project level (visible / private), not per roadmap item and not per work-log entry.
2. "Private project" access is controlled by a global usergroup permission (viewPrivate), not owner-based rules.
3. Roadmap/work-log access is controlled by global usergroup permissions (viewRoadmap, viewWorkLogs) plus project-level privacy, not per individual entry.
4. There is no "private reply" model in this addon. Work logs do not have a per-entry visibility field.
5. Roadmap items can optionally link to a XenForo thread via "thread_id", but items and work logs themselves are not XenForo threads/posts.
6. XenForo custom thread fields are not integrated into project items, and the addon currently does not provide a custom-field system for roadmap items/work logs (it does support custom roadmap item types).

Important migration limitation:

• Roadmap items and work logs are intentionally short-form:
  • Roadmap items: up to 150 characters
  • Work log entries: up to 255 characters
• They do not support attachments.
• So they are not designed to replace full forum-thread/post discussions or document storage.

What the addon is designed for:

• Short roadmap entries and concise dev updates/logs
• Progress/status tracking
• Watch/follow notifications
• Milestone/status activity alerts

Your use case is valid, and you are welcome to post it in our suggestions area. We can consider it for future updates, including:

• Per-entry visibility for roadmap items and work logs
• Optional owner-based access rules
• Migration-safe enhancements based on existing data structures

So in short: this specific vBulletin Project Tools mixed-visibility model is not supported out of the box yet, but it is a realistic candidate for customization/future enhancement.

 

[Veer]

Veer updated [XenCustomize] Project Tracker with a new update entry:

2.3.1 - New Features & Enhancements

XenCustomize Project Tracker 2.3.1 Released​

We're pleased to release Project Tracker 2.3.1, a polish-focused update with several usability, styling, and quality improvements.

This version improves the Project Insights chart system with a cleaner monthly timeline, paged navigation for older data, and inline AJAX navigation without full page reloads. We also improved chart visibility in dark mode for better readability across styles.

On the project view...

Read the rest of this update entry...

 

[ratix_gunz]

I think it's a superb add-on!

I bought it a week ago and I don't have much to say except that a few options are a bit unclear or cluttered for my taste. Otherwise, it's truly flawless, and the layout is very modern and professional!

There is one small feature that is a bit "rough" for me because I was tricked at first: it is the fact of clicking on the raw name of the project to display the roadmap.
I think we should add an extra "View project" button next to the "View product" button or something else because for an average user, they will first click on the "view product" button and will not realize that a roadmap can be read.
We need to highlight a way to make it clear that there is a roadmap and not just a page with a history.

In any case, it's not a problem at all because I haven't experienced any bugs, issues, or anything else, and everything runs very smoothly.

This is the first time I've purchased an add-on from you, and I'm very satisfied!

 

[Veer]

Thank you very much @ratix_gunz, for the kind words and for the helpful feedback.

We’re really glad to hear everything has been working smoothly for you. Your point about the roadmap link is a good one too. It makes sense that some users may click “View product” first and not immediately realize the project title opens the roadmap, so that’s something we’ll keep in mind for a future improvement.

We really appreciate your support, and we’re especially happy to hear your first purchase with us has been a good experience.