[ABD] Ticket Tracker

[eunaumtenhoid]

nice work
system of notification?
for new comment
ticket closed
etc

[nou nou]

Absolutely fantastic looking! Very exciting!

[Kailey]

nice work
system of notification?
for new comment
ticket closed
etc

The extension isn't even halfway finished. Yes, notifications are planned.

[nou nou]

And I bet permissions for those notifications are as well?

[Kailey]

I don't understand this statement. What do you mean "permissions for those notifications"? Notifications are just that - a mechanism for notifying users of a certain action. They aren't tied to permissions.

[eunaumtenhoid]

ty for reply

will be very welcome a button in tickets for adm / mod / ticket author to mark the same as "resolved"
will it be possible to add new trackers or will it only be those predetermined?

[nou nou]

I don't understand this statement. What do you mean "permissions for those notifications"? Notifications are just that - a mechanism for notifying users of a certain action. They aren't tied to permissions.

Oh, right.

A permission for being able to receive notifications, especially if there is an ability to subscribe to everything. I'm a little worried about potential email quota issues.

[nou nou]

Or perhaps it's a permission to subscribe, rather?

[Kailey]

will be very welcome a button in tickets for adm / mod / ticket author to mark the same as "resolved"

"Closing" the ticket can be done by those users who have that permission (I haven't coded that part yet).

will it be possible to add new trackers or will it only be those predetermined?

It is technically possible to add new trackers since they all reside in the database. However, due to how the tables are interlocked, I'll have to figure out the best way to approach this.

Or perhaps it's a permission to subscribe, rather?

A "Can subscribe to (tracker, project, ticket)" should be possible. I'll address this when I get to the permissions stage.

[nou nou]

Sounds great!

About the month picking. Martti has all those calendar helper extensions going on, perhaps something from that can be of use?

Edit: nvm, seems that would be a little overkill for what you're after...

[eunaumtenhoid]

NICE
will a voting system be implemented?
to measure that more than one user has already had the bug or a bug to give priority?
or to filter out bug as top voted among other possibilities?

[Kailey]

will a voting system be implemented?
to measure that more than one user has already had the bug or a bug to give priority?
or to filter out bug as top voted among other possibilities?

No, that would be outside the realm of this extension.

[nou nou]

I was wondering about ticket identifiers. Bug tracking systems often allow for assigning a number to a specific bug (sometimes called an RFE number) which can then apply to several bugs (repeat reports, for example). It's not the same as the ticket number.

So a bug gets reported or a feature requested, questions are being asked and when the bug or request is confirmed in a post, that post is then assigned that RFE.

Further duplicate reports can then refer to, and be assigned, that number, too.

On the next release, a change log can then contain all the relevant RFE numbers for easy reference.

Would that be something that could be covered by your extension?

[Kailey]

More complicated than need be. If there are duplicate reports, there's an option to mark it as duplicate and then reference the ticket number that the report duplicates.

[nou nou]

Yup, that works for me! Thanks