This would be great. We're using Mantis a bit currently and Jira is always mentioned. It would be great to get at least this level of functionality.
Better yet...perhaps the ticket module would allow for an external connection to an existing bug system? Problem is that we love the aC interface/experience.
For those of us willing to hack on AC, are there any pointers in how to attack such a feature? At this point, this is appearing to be the one thing that may prevent us from being able to use AC. All we need is a way to separate "resolved" from "verified". Workflow would probably be great, but we really need a way to make sure that bugs are actually verified before being marked completed.
I'm considering using categories, and modifying the templates to make it easier to set the category. I've seen some suggestions of using categories. Has anyone had any success with this kind of approach.
Planning Module looks interesting, but I need to know more about it. The demo on the website seems to be a mock-up rather than a real AC install, so it's hard to see how it integrates with the existing system. I found the "card" interface (at least on the website) much harder to use and understand than the built-in AC interface. But this may have been a function of the demo; it was hard to evaluate.
@Rob: The hack to add additional statuses for tickets can be done via categories or via adding a new field.
You can create categories for Open / Resolved / Verified etc. And move tickets from one to another. You can even use mass edit on the tickets list to move selected tickets to another category.
This is how we started managing ticket statuses. But overgrew it and hacked AC to add a new field for workflow_status and a whole lot of related hacks. We will plan a small write up on these hacks in the future so that other people can learn from them as well.
As for Planning module demo - yes, the header / footer are simply images. The project plans are also dummy. The card view is to manage details of tickets / pages / checklists. The way we use it, is define overall items using Outline view. then add detailed requirements using cards view.
You may want to checkout our TicketsPlus module which allows you to create custom workflow status of Tickets. You can create any number of workflow statuses and change the status of the Ticket.
> open
> pending
> solved
and then create an accompanying styling for each to indicated the status of tickets.
this is helpful when some of the tickets are partly done, but not yet complete.
thanks!