Issue label and status

[vimishor]

Application looks very nice, but I miss labels and status for issues. Any future plans for this ?

[deplorableword]

Status do you mean: on-hold, fixed etc?

[vimishor]

Exactly. Those are the "standard" statuses, that are encountered very often. But it would be nice to allow administrator to define his own custom ones, like "not approved", "needs testing", "waiting for feedback" and so on.

[deplorableword]

If we were going to make a change, I would prefer we go with a boilerplate set of 5 commonly understood statues.

Allowing arbitrary statuses is much bigger change and makes translation / UI much more complex.

[vimishor]

Sound good enough for me. Unfortunately, I've just started to look around in Laravel's documentation and I'm not the right man for this task. Maybe someone who knows the framework will transform this idea in a fact.

[mikelbring]

I think the best direction to go is with a tagging system. So that it leaves more flexibility to the users on how they want to use the system. Either they can use tags as status, categories or a combination of the both. With the ability to search tags.

[deplorableword]

Sounds interesting.

How do you imagine you could change an issue from 'open' to 'on-hold'? Traditionally the UI might look like a dropdown, but with tags would you need to remove 'open' and add 'on-hold' tag? Would we use some kind of tokenized text-input? Checkboxes?

On 20 Jul 2012, at 07:04 PM, mikelbringreply@reply.github.com wrote:

I think the best direction to go is with a tagging system. So that it leaves more flexibility to the users on how they want to use the system. Either they can use tags as status, categories or a combination of the both. With the ability to search tags.

---

Reply to this email directly or view it on GitHub:
#64 (comment)

[vimishor]

@deplorableword Maybe an input box with auto completion and next to it show 2 - 3 most used tags, or tags related to the age of the issue.

Something like this maybe:

• If the issue is new, suggest tags like "accepted", "not a bug", etc
• If the issue already has one of the above tags, suggest o new list with tags, like "needs testing", "fixed", etc

Just a raw idea.

[deplorableword]

Interesting, I think the database stuff will be the easiest part of this. Think the tricky part is going to be making the UI awesome and easy to use...

[ajira86]

If nobody has the time, I'll start to develop it. I will create a branch in my fork the next days and push it in github if your are interesting.

[ajira86]

Hi,
I started to work on it but it will be easier to work with the latest version of laravel framework (3.2) who allow to use sync method in has_many_and_belongs_to relation

[ajira86]

I tried to update it but I have many issue during laravel upgrade from version 3.1.9 to 3.2, can someone help me ? I'm not an expert with this framework :P

[ajira86]

So, I found a way to upgrade laravel to version 3.2 with an update in login system.

Work continue, I'll commit soon ;)

[nodiscc]

Is this a duplicate of #23 ?