d***@gmail.com
2015-09-07 16:34:51 UTC
Hi,
We recently upgraded to the latest trac and agilo versions and have
observed a rather annoying bug with the ticket type since.
When modifying a ticket, it does not pre-select the ticket's type from the
dropdown (even though it's shown clearly in the title) so when submit it
changes the ticket type to whatever the first entry was. Tested this on a
stock trac+agilo project with no upgraded data or customizations and
observed the issue. The stock trac (1.0.8) without agilo, previous versions
(trac 0.12 + agilo 0.9.9) and your live demo (1.3.14-PRO) are able to
detect and select the appropriate type in the combobox.
Steps to reproduce
prereqs:
* reorder Ticket Types (if not already): Task, Bug, Story, Requirement
* remove stock "defect" & "enhancement" Ticket Types (or move to bottom,
doesn't matter)
1. Create a new Bug ticket
2. Open the new ticket and make a change
3. Click Submit Changes
Expected:
Ticket Type selected is Bug, changes made and ticket type remains Bug
Actual:
Ticket Type selected is Task, changes saved but ticket is now a Task
Observations:
I'm a developer and was curious so I dug around in the python code for a
bit and got as far as getting it to log the data it received back from the
database and the dictionary used to populate the fields. It appears to
always have 'defect' set for the field value even though the SQL returns
the correct type and the page header is correct...perhaps the issue is in
that area or it's getting lost in translation?
Let me know if anything else is needed to resolve the issue.
Versions:
python 2.6
Trac-1.0.8
agilo-0.9.14 (not pro)
Thanks,
Deb
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum
You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.
To post to this group, send email to ***@googlegroups.com
To unsubscribe from this group, send an email to
agilo+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/agilo
---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
We recently upgraded to the latest trac and agilo versions and have
observed a rather annoying bug with the ticket type since.
When modifying a ticket, it does not pre-select the ticket's type from the
dropdown (even though it's shown clearly in the title) so when submit it
changes the ticket type to whatever the first entry was. Tested this on a
stock trac+agilo project with no upgraded data or customizations and
observed the issue. The stock trac (1.0.8) without agilo, previous versions
(trac 0.12 + agilo 0.9.9) and your live demo (1.3.14-PRO) are able to
detect and select the appropriate type in the combobox.
Steps to reproduce
prereqs:
* reorder Ticket Types (if not already): Task, Bug, Story, Requirement
* remove stock "defect" & "enhancement" Ticket Types (or move to bottom,
doesn't matter)
1. Create a new Bug ticket
2. Open the new ticket and make a change
3. Click Submit Changes
Expected:
Ticket Type selected is Bug, changes made and ticket type remains Bug
Actual:
Ticket Type selected is Task, changes saved but ticket is now a Task
Observations:
I'm a developer and was curious so I dug around in the python code for a
bit and got as far as getting it to log the data it received back from the
database and the dictionary used to populate the fields. It appears to
always have 'defect' set for the field value even though the SQL returns
the correct type and the page header is correct...perhaps the issue is in
that area or it's getting lost in translation?
Let me know if anything else is needed to resolve the issue.
Versions:
python 2.6
Trac-1.0.8
agilo-0.9.14 (not pro)
Thanks,
Deb
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum
You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.
To post to this group, send email to ***@googlegroups.com
To unsubscribe from this group, send an email to
agilo+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/agilo
---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.