ticket,summary,type,release,owner,status,created,modified,_description,_reporter
13729,Wrong table layout in the groups,defect,1.4,thomasd,new,2020-01-10T12:19:25+01:00,2020-01-10T12:58:42+01:00,"While the core Trac always has a 2 column table layout with all text fields sized to the max length, the grouped layout of GroupTicketFieldsPlugin has some issues as demonstrated in the **attached screenshot**.
* Text fields like Developer, Issue reference and also textarea fields like issue description are shorter than the column width
* The column width inside group ""Release notes"" for Issue reference and Risk is not equal and different from the other column width of the same group
* The text area column widths of the group ""Release notes"" are not equal on the left and right side, like ""Configuration notes"" vs. ""Technical notes"".
Please note:
this version of GroupTicketFieldsPlugin is patched with [[comment:1:ticket:10469]] and has a linebreak after ""Affected modules"". The style.css is patched to have a decent max-width of 1400px on our teams screens.
This is the part of the configuration:
{{{
#!ini
[ticket-custom]
issueref = text
issueref.label = Issue reference
issueref.order = 80
issuedesc = textarea
issuedesc.label = Issue description
issuedesc.order = 81
issuedesc.format = wiki
issuecause = textarea
issuecause.label = Issue cause
issuecause.order = 82
issuecause.format = wiki
changedesc = textarea
changedesc.label = Change description
changedesc.order = 83
changedesc.format = wiki
affectedmod = text
affectedmod.label = Affected modules
affectedmod.order = 84
risk = select
risk.options = |high|medium|low
risk.value =
risk.label = Risk of side effects
risk.order = 85
impact = textarea
impact.label = End-user impact
impact.order = 86
impact.format = wiki
config = textarea
config.label = Configuration notes
config.order = 87
config.format = wiki
technicalnotes = textarea
technicalnotes.label = Technical notes
technicalnotes.order = 88
testnotes = textarea
testnotes.label = Test notes
testnotes.order = 89
[group-ticket-fields]
group_order = project, main, roles, releasenotes, extra
extra = Extra
extra.fields = ccb_prio, ticketsboard, totalhours, estimatedhours
extra.properties = foldable, collapsed
project = Project
project.fields = project,component,version,type
roles = Roles
roles.fields = developer, development, reviewer, review, tester, test, editor, documentation, serviceer, service, integrator, integration, propagation
releasenotes = Release notes
releasenotes.fields = issueref,risk, affectedmod, -, issuedesc, issuecause, changedesc, impact, config, technicalnotes, testnotes
}}}",Massimo
13705,Layout ticket view,enhancement,1.4,thomasd,new,2019-12-03T10:18:49+01:00,2020-12-03T06:01:44+01:00,"Hello,
the GroupTicketFieldsPlugin has become very important since TracTicketFieldsLayoutPlugin is deprecated, as discussed in gdiscussion:trac-users:kjQqYdxWd90.
While the **ticket editor** layout can be customized with this plugin in a nice way, there is no layouting at all for the **ticket view**. Could you implement setting the same groups (group boxes) and layouting for the view as well?",Massimo
13704,Renaming main group,enhancement,1.4,thomasd,new,2019-12-03T09:49:52+01:00,2019-12-03T09:50:16+01:00,"How can I rename the internal group 'main'?
The main group by default has the name ""Properties"". Adding
{{{
[group-ticket-fields]
main = Main
extra = Extra
extra.fields = ticketsboard
group_order = main, extra
}}}
gives a weird result:
The main group is named ""Main"", but gets all fields. Then there is the empty group ""Extra"", and another empty group ""Main"".",Massimo
11567,grouping ticket_type causes header to break in ticket_box.html template,defect,1.0,thomasd,accepted,2014-02-12T20:04:42+01:00,2015-03-10T10:54:20+01:00,"A defect in this plugin breaks header ordering on ticket_box.html template when placing ticket_type into a group.
How to reproduce:
{{{
[group-ticket-fields]
group_order = ticket_type
ticket_type = Ticket Type
ticket_type.fields = type
}}}
'''What happens'''
{{{
#!html
}}}
",Russell Ballestrini
11407,Groups Not Persisting with Conditional Tickets,defect,1.0,thomasd,new,2013-11-22T22:58:47+01:00,2013-12-03T16:49:56+01:00,"I am using the Conditional Field Plugin and when I initalize a new ticket the group is displayed correctly, but then when I change the ticket the fields within the group are reverted into the main group.
Is there any way for the group to stay intact even when the ticket type is changed, and just remove the fields within the group that are not associated with the that particular ticket type?
Thanks,
sgcode",sgcode
10470,Can't move radio buttons,defect,0.12,thomasd,new,2012-10-11T21:28:07+02:00,2012-10-11T21:28:07+02:00,"The DOM structure of radio buttons is quite different from that of other field types. There is no ""label for"" the input to key on and no unique input field with the ""field-"" as the ID.
It looks like:
{{{
Confidence:
}}}
whereas the same choices as a select look like:
{{{
}}}",Chris Nelson
10469,"[patch] Add a ""skip this cell"" pseudo-field",enhancement,0.12,thomasd,reopened,2012-10-11T20:38:44+02:00,2021-05-29T21:20:40+02:00,"I'd like to be able to configure:
{{{
[group-ticket-fields]
group_order = relationships,main
relationships = Relationships
relationships.fields = parents,-,blockedby,blocking
}}}
And have the fields arranged:
||Parent ticket||||
||Depends on||Required for||",Chris Nelson
10343,hide groups if all grouped fields are hidden,enhancement,0.12,thomasd,new,2012-09-19T18:16:24+02:00,2016-04-18T14:33:18+02:00,"Would it be possible to hide the group section in the ticket if the grouped fields are hidden? We currently use [http://trac-hacks.org/wiki/DynamicFieldsPlugin DynamicFieldsPlugin] that allows us to hide fields, but when all the fields are hidden from the group, the ""group"" window is still there and confuses some users.",anonymous