Page 5 of 7

Re: [3.2][DEV] Ticket Tracker

Posted: Thu Feb 21, 2019 12:23 pm
by eunaumtenhoid
nice work
system of notification?
for new comment
ticket closed
etc

Re: [3.2][DEV] Ticket Tracker

Posted: Thu Feb 21, 2019 3:14 pm
by nou nou
Absolutely fantastic looking! Very exciting!

Re: [3.2][DEV] Ticket Tracker

Posted: Thu Feb 21, 2019 6:38 pm
by kinerity
eunaumtenhoid wrote:
Thu Feb 21, 2019 12:23 pm
nice work
system of notification?
for new comment
ticket closed
etc
The extension isn't even halfway finished. :lol: Yes, notifications are planned.

Re: [3.2][DEV] Ticket Tracker

Posted: Thu Feb 21, 2019 9:29 pm
by nou nou
And I bet permissions for those notifications are as well? :)

Re: [3.2][DEV] Ticket Tracker

Posted: Fri Feb 22, 2019 12:00 am
by kinerity
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.

Re: [3.2][DEV] Ticket Tracker

Posted: Fri Feb 22, 2019 6:26 pm
by 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?

Re: [3.2][DEV] Ticket Tracker

Posted: Fri Feb 22, 2019 8:37 pm
by nou nou
kinerity wrote:
Fri Feb 22, 2019 12:00 am
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.

Re: [3.2][DEV] Ticket Tracker

Posted: Fri Feb 22, 2019 8:40 pm
by nou nou
Or perhaps it's a permission to subscribe, rather? :)

Re: [3.2][DEV] Ticket Tracker

Posted: Fri Feb 22, 2019 8:48 pm
by kinerity
eunaumtenhoid wrote:
Fri Feb 22, 2019 6:26 pm
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).
eunaumtenhoid wrote:
Fri Feb 22, 2019 6:26 pm
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.
nou nou wrote:
Fri Feb 22, 2019 8:40 pm
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.

Re: [3.2][DEV] Ticket Tracker

Posted: Sat Feb 23, 2019 12:32 am
by 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...

Re: [3.2][DEV] Ticket Tracker

Posted: Sun Feb 24, 2019 3:15 am
by 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?

Re: [3.2][DEV] Ticket Tracker

Posted: Sun Feb 24, 2019 5:42 pm
by kinerity
eunaumtenhoid wrote:
Sun Feb 24, 2019 3:15 am
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.

Re: [3.2][DEV] Ticket Tracker

Posted: Fri Mar 08, 2019 5:15 pm
by 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?

Re: [3.2][DEV] Ticket Tracker

Posted: Fri Mar 08, 2019 9:24 pm
by kinerity
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.

Re: [3.2][DEV] Ticket Tracker

Posted: Sat Mar 09, 2019 2:33 am
by nou nou
Yup, that works for me! Thanks 😀