Feature Requests

Minor UI feature request. When someone is doing a Visio or CAD drawing, and they have the project editor open on the side, with the list grouped by location or system, or both, if there are too many items in a location, and we scroll down, the location name is hidden. It can be a good idea to pin the current location name/group name on top while scrolling down a long list, and it's replaced by the next group name/title as soon as we scroll to the next one and the previous is hidden.

clicker games online combine simplicity and strategy, making them perfect for players who enjoy steady growth and engaging mechanics without overwhelming complexity.

Hello D-Tools team and community, After reviewing many feature requests on this platform, I believe one of the most impactful areas for long-term product growth is how user feedback is collected, contextualized, and transformed into actionable improvements. While D-Tools already provides powerful tools for system design and project management, refining the feedback loop could significantly improve both usability and adoption over time. In many modern digital products, especially interactive web platforms, user behavior and feedback data play a crucial role in shaping feature roadmaps. This approach is not limited to enterprise software. For example, lightweight browser-based video games often rely heavily on real-time user feedback to optimize engagement. A good example is Slice Master> , a reflex-based online game available at https://slicemaster.net/ , where gameplay simplicity is continuously refined based on how users interact with the mechanics, pacing, and difficulty progression. What makes this relevant to D-Tools is not the genre itself, but the principle of rapid feedback and iterative UX improvement. By observing where users hesitate, repeat actions, or abandon workflows, developers can prioritize features that truly solve real problems rather than assumed ones. Suggested Feature Request: Context-Aware In-App Feedback System Description: Introduce an in-app feedback tool that allows users to submit feature requests, usability concerns, or bug reports directly from the screen they are working on. Each submission could automatically include contextual data such as the active module, workflow step, or recent user actions.

I understand we can do @mentions and chat in a ticket already but sending an email or giving a little green alert up top is super inefficient, ideally this would push to a notification on the app..

ability to add note for each change item so in report we can show to customer the reason for deleting/adding/modifying each item or aggregated group of items.

Can we add 2x Site Notes Sections and the ability to include or exclude them from reports? So often, we would like to send a report to the client with Site Notes included, but we would also like to add more technical information that does not necessarily need to go on the customer-facing report. It would be great to have the following: Site Notes (Customer) Site Notes (Internal)

We need the ability to add project specific headends. For example while there may be only one MPOE/MDF there are often several IDFs that each have their own room numbers that we need to reference as a headend. Same for CAB#s etc. Please add the ability to enter custom headend per project without affecting global headends.

Whether or not we have a model number for a chosen wire selected, we would assign it a schedule ID to reference a cable schedule in our legends. For us, we created Custom Field 1 to be an items 'Schedule ID' so we can assign a moniker to each wire that is specific to each project. It would be rad to be able to create a custom product schedule in each and every DT project, I would love to work with DT on creating that, for now, I don't necessarily want to show the make/model of the bulk wire on my plans, rather we need to be able to call it out by it's moniker as the same schedule id is not used for every project. For example, we designate schedule ID 'S1W' to be a specific make/model white 14awg plenum rated speaker cable as part of our standard cable schedule for projects we design. However another engineering firm who provides us with a constuction set of drawings with their own custom wire schedule with different make/model bulk wire, we would also then designate 'S1W' for their specified white 14awg plenum rated speaker cable instead of ours. Thus, the schedule ID becomes more important that the actual make/model so we need to show the schedule ID and not the make model.

When we import a price list from a supplier we would like the import tool to show us if there has been a price increase in cost to what is currently in the database so we are aware of any major price changes. If we could set a threshold for the notification for example 15% increase that would be great.

Need a way to import/export checklists. Maybe a csv or notepad or RTF file where a new line represents a parent node, and the child nodes can be denoted with ">" symbol