Allow editting of field types other than "select"

[Jason Winnebeck]

I evaluated this plugin to see if it could modify custom ticket fields. I tried in a new environment with a text field, and did not see any box to edit.

Rationale for the requirement:

Currently at my organization we use a tool called ScrumWorks to do agile planning and estimation and I'm looking at plugins for Trac to try to emulate the behavior (rather than using 2 products). In this tool, it displays a list of sprint tasks (SBIs) in a table format with the work remaining. In our agile environment the team does a "daily standup" and updates all values together in the meeting. In Trac we could do this with a custom field and update, but we would have to click each ticket. I was hoping this plugin would allow us to update all tickets from the same screen.

I rate this as a low priority, because I'm still not sure if we would want to use Trac for this, for reasons beyond multiple ticket editing.

Nice job on this plugin, and it's an awesome idea, plus it is great how it requires no configuration and integrates seamlessly.

[anonymous]

Custom fields are supported but currently ONLY "select" type fields are supported (whether they are custom or built in).

I plan to add in support for text, checkbox, and radio fields eventually but at the moment our business requirement doesn't include these. Including other types would be pretty easy and I welcome patches if anyone wants to do it before I do.

[Jason Winnebeck]

I think I was confused by the term "select" fields. I guess you are saying it will support even custom fields as long as they can be represented by a dropdown menu (combo box)? OK, it makes sense now when I look at the list of types of TracTicketsCustomFields. I'm not sure why I didn't associate select there. I was thinking actually of SQL SELECT, as if it had to be from a column in a report.

This might be a fun thing to submit a patch for (learning JS/AJAX/Python), but I don't think we're going to use our Trac for Scrum after all (and therefore don't need a custom text field or the ability to modify it through the plugin).

So, unless others out there want it, I would say this is a low priority.

[peter@…]

The EstimationToolsPlugin solves exactly the user story you describe here. I'm using it for my projects, and I highly recommend it.

[Jason Winnebeck]

From the plugin description, it looks like it only allows you to edit the hours remaining quickly. Is what you mean is to use this plugin for editing the "normal" fields but EstimationToolsPlugin still lets you edit the estimated hours remaining? That might be a fun combination, that way we can edit the values during daily standup like a spreadsheet.

[peter@…]

Yes, I agree with what you suggest.

[Jason Winnebeck]

OK, I am installing both plugins now to see how it goes. I realized with the combination of these two plugins, I can create a "daily standup" page on the milestone with a custom query and the burndown charts, and be able to edit all fields on the fly.

[Abbywinters.com WebDev]

(In [6614]) * Improved performance of GridModifyPlugin by changing Genshi transforms to jQuery transforms using patch from #3531 (thanks mmastrac)

• Provide graphical feedback for AJAX actions using patch from above.
• Provide support for field types other than select (closes #3651 and #5364)
• Provide the ability to exclude some fields from being grid modifiable in trac.ini
• Add verbose debug logging.