+2
Under review

Custom fields

Marie-Claude fa 10 anys updated by tech fa 9 anys 3
Once a month I return here to see the progress of Damnbugs and its new features. I was curious to see the development of the ''TAGS'' section. It seems really great, but I still have a question about that.

I'm working for an elearning company. The bug tracker we are currently working with allow us to create different custom field (String, list, checkbox, numeric, drop-down menu).

For exemple, we have a ''Departement ID'' that allow us to select from a drop down menu the departement that are responsible of the issue. (Production, programmation, Pedagogy...)

We also have a string custom field that allow us to write the screen number where the issue was found. We often have 100 screens projects, so it would be hard to put them into the 'tags' section. We also need to see the screen number (and some of our other custom field content) in the bug list table.

+1
Under review
Bonjour Marie-Claude,

It sounds like you have a rather complex, unique situation. Tags could be used to achieve this but it does sound like a lot of work.

We build features based on how many users request them; I'll leave this open to see how many votes it gathers and if it seems popular enough, we'll do it!

Simon



I just wanted to know if there is any development on this subject. I saw that we now have the ''Bug type scheme'' section which is really usefull. I also use the ''project section'' field to specify the department (Narrator, Pedagogy, Production, Client. It helps us with the statistics of our project and to see if some employee would need more training.), but I still would need to add some other fields.

Example :
# Capsule/Module (Numbered drop down menu)
ID of page ( Text field )
Language (Text drop down menu or radio button )



Hi Marie-Claude,


While it does sound like something useful for more users than just your team, given that we are a very small team we have to prioritize what the features that we work on and we haven't reach this point yet.


We will however, dig further into the Browser extension issue you reported starting next wednesday (March 1st)


Thanks for checking in, we appreciate your interest in our tool!