Issue Tracker? Anyone?

Mark

@Toivo - exactly. I'm thinking that maybe a qualified few will be able to go through this forum and mark actual discussions as bugs - then they appear in the bug tracker. Sort of the opposite of how add-ons work now...

Mr Do

@Tivio and Mark: I think I would prefer the suggestion I made above about having 4 different access level on roles, but I guess this could be handled any number of ways. One way could be to have level 4 users (read and comment on issues only) have the option to "submit issue" where what actually happened, was that it got sent to a certain role, who could create an issue based on it. (Technically a private message). @jazzman: I got my coworkers to agree to test this out. So how long before we can start testing? Is there anyway I can help out? and btw, a small feature request list: - email moderators (in essence project workers) about new issues - email or external issue submitting - project works get a "to-do" list based on the issues their assigned to. - issues divided into emergency bugs, bugs, feature requests, planned features. These can be just tags that are can be searched and/or filtered. - integration with svn logging would probably rock :) anways, thanks for making this, and if u can manage to put in one or more of my feature requests, that would rock :)

TomTester

I'd like it as a forum template. ;-)

Love the drop-downs at the top for project (category) selection, and those two extra fields (status & priority)
are good too (I would rename these to status (new, hot etc). and 'rating').

Five suggestions:
#1 - enable/fix the discussion tags add-on (issue tags?) for the tabled theme (on my wish-list)
#2 - create the long-desired 'smart submission' add-on that checks for similar 'issues' (discussions) upon submission to avoid duplicate issues (posts)
(http://lussumo.com/community/discussion/4377/related-posts-similar-discussions/)
#3 - create the intra-forum (issue tracker) link preview for quick, no-click navigation (show first 30 words of issues/comments linked to on roll-over)
(http://lussumo.com/community/discussion/4227/intravanilla-link-preview/)
#4 - 'fix' vanilla search to search through TITLES and COMMENTS at the same time
#5 - create a tag-based 'issue filter' for big projects (and big forums)

Mr Do

Jazzman. how goes it?

Jazzman

Once It's a bit more stable and ready for alpha testing, I'll let you know But for now, things like assigning a user, sorting, etc still doesn't work.

Jazzman

Making progress here It could turn out to be a Lighthouse clone (It's not a mockup! This screenie is real!!):



I've added three new fields:
1) Status: open, resolved, invalid and on-hold
2) Classification: bug, feature-request
3) Priority: Low, Medium, High

You can filter on these three fields. Each field can have other values. Status could have: Open, Closed, Done, Removed, Implement, whatever

@ Mr Do, You have nice ideas, but I'm not going to implement those. It will be an addon, you're talking about a whole new application

Most important rule: keeping it simple!!! It's still going to be Vanilla Just a few extra fields and a more ticket-theme-look!

Dinoboff

Wow, that's looking so good.

Mr Do

jazzman: So an issue can no longer be assigned to a worker? some of the features that I mentioned could be made as extension on your extension though right? Are you going to submit it soon?! :)

Jazzman

The normal role-model applies here Mr Do, you'll have extra permissions to change status, priority and classification fields. Let's say a reporter-role can add an issues and set the priority, where developer-roles can change the status, etc. But to answer your question: yes, you can assign an issue to a user He/she gets his/her own list of assigned issues.

And yes, you can create extensions on this extension

It will be finished next week!

Mark

That is so awesome.

y2kbg

haha i know,
dude you are the man!!!!

Krak

speechless.

Austin

I cannot wait to get my hands on this.

Crypt

Geeze this is looking slick.

Jazzman

I came across an issue: when using discussions and categories for issues and projects, I found out that when using multiple projects the ticketnumbers weren't matching. So you have Project A, with tickets 1, 2 and 3. When creating a ticket for Project B, it would result in ticket number 4.... So I fixed that, by starting to count from 1 at each project... But in the overview selecting "All projects" will result in multiple tickets with 1, 2, etc.

What do you guys suggest? Keeping the issue number unique? Or just proceed this way? When you have different clients, and they can only few their own project, it could seem weird when they're numbers go: 7, 8, 15, 16, 18, etc. But when you view multiple projects, it will also be weird seeing the same ticketnumber more then once... Any suggestions?

Mr Do

unique numbers for projects of course. all issues within a project must be sequential. that you get identical numbers cross project isnt a big problem the way i see it. one thing you can do is do projectid_issueid when listing multiple projects. I suspect that one will very seldom want to see issues from more than one project at once

TomTester

How about making the overview display ticket numbers unique by combining PROJECT# and TICKET#
(i.e. just display PROJECT#-TICKET# on the overview page)?

Benefit: ticket number has 'internal reference' to the project.

If you wanted to go really overboard, also insert the ticket opened date in the ticket ID.

Stash

What they said That way you can have an admin account that can view everything and limited accounts that can only view one (or 2, 3, 4 whatever you specify). I assume the project and tocket IDs can increment infinitly?

MySchizoBuddy

So u have two options
Ticket #234, or Ticket #3 of Project #6

I'll pick the first one. thats how other issue tracker do it as well. simple number, no need to worry about which project that ticket belongs to
here is a sample conversion

"Look at ticket #3 of project #6"
"I am, that ticket is nothing to do what ur saying"
"dude look carefully its about blah blah"
"No its about yada yada"
"Ops sorry, my bad. Its ticket #6 of project #3"
"Thanks for wasting my time"

Tracking one number is always better than tracking 2, don't u think so

Mr Do

id rather do Thicket #6_3 or #6003 or something.. If a person lists all the thickets on projects it is bad if it lists : Thicket #1 Start up project Thicket #15 Create name for project Thicket #17 Post name of project If there are just 3 thickets and they have such numbers because the missing numbers are on another project the person doesnt have access to, thats bad. IMO.