Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.
Two ideas of evolution
First: In the menu "work-> Tickets" we do not see what version of the evolution bug or are planned. I suggest adding a column "version". This allows us to know:
1) the target for the tickets "accepted"
2) the software version for tickets "delivered"
Second: We use a unique number (track) for all tickets. It tracks
- Evolution / Support and problem.
I suger have a unique numbering for bugs, it would follow with a unique all bugs (bugs tracking database)
Sorry, I don't undesctand your post.
Is it a request ?
Could you explain ?
.. or maybe it was just a hard day's night ... 😉
sorry I'm very tired 🙂
I corrected my original post ....
Two ideas of evolution
First: In the menu "work-> Tickets" we do not see what version of the evolution bug or are planned. I suggest adding a column "version". This allows us to know:
1) the target for the tickets "accepted"
2) the software version for tickets "delivered"
Second: We use a unique number (track) for all tickets. It tracks
- Evolution / Support and problem.
I suger have a unique numbering for bugs, it would follow with a unique all bugs (bugs tracking database)
Hi,
I registered your request in Track Database :
Add column version on ticket list : ticket #463
Good idea, easy to implement. I will just have to "find some place" in the list for this column
unique numbering for bugs : ticket #464
If I understand, it would be to get an extra numbering dedicated to each type. Am I right ?
A planned evolution is to add an 'external reference' (to be abled to refer to any external tool.
Could it answer your request or do you expect an automatic numberin ?
Thanks for your ideas.
Thanks,
The objective is a unique numbering for problems and evolution (not for support)
Incorporate a small "Bugzilla" in projector
Other : It would be nice to add the concept of duplication for the problems (seen after analysis).
Idea : define a template for numbering :
May include {project}-{element}-{type}-{n°}
So you may define :
{project}-{n°} : to get a unique number for each project, but common numbering for all elements
{type}-{n°} : to get a unique number for each type, but common numbering for all projects
an so on...
Could it fit your need ?
For duplicate : ticket #466 registered
Good idea.
Yes.
The priority is to get a unique number for each project for each type (Bug/support/evolution)
{project}-type}-{n°}
Thanks
PS: Ticket 399 is very important 🙂 =>It's very long to create a set of activities and milestone redundant ... Whereas with copy / paste would be top!
And congratulations for your work and your reactivity!