need way to rename components safely
| Project: | Project issue tracking |
| Version: | 5.x-2.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | dww |
| Status: | active |
Jump to:
right now, if project admins go to the edit tab on their project nodes, click on the issues subtab, and modify any existing components, the DB is left in a somewhat lame state where all issues and follow ups that ever used the old name still use the old name, and when you try to follow up again, it's flagged as a validation error and you have to select a new component manually.
instead of a text area that you can edit freely, there should be a table of the current components, with "rename" and "delete" operations, and a text field to add a new one. if you click "rename", it should bring you to a page where you enter the new name, and if you press "submit", it will go through and repair the DB to fix all existing issues and followups for the project that referenced the old name, in addition to fixing the record in the {project_issue_projects} table.
#1
subscribe
#2
#3
@hunmonk: i know you're trying to clear out the issue queue, but i'm not convinced that just marking things you don't want to work on as "postponed" is the most helpful approach. ;) for example, there are a handful of drupal core components on d.o we'd like to rename, if we had this working. sure, it's not top priority, but that's why this isn't marked "critical". in my mind, "postponed" means it's basically blocked on some other specific issue or event before we can make progress on it. in this case, it's just a question of getting around to it -- it's not blocked on anything except having time to work on it.
#4
@dww: c'mon, dude -- you know me better than that. :)
imo there was a perfectly valid reason for marking this postponed (along with many other issues) -- i judged it as something that was best fixed on the next major branch. that's a perfectly valid reason for postponing an issue, and it makes the issue queue easier to manage for the issues that are of current concern.
now that project issue has been branched for DRUPAL-5, it makes sense to me to mark this as active again.
note: imo, one of the reasons the postponed status is so rarely used is because currently it's a pain in the ass to mass edit issue states. if i wasn't, i think we'd use this kind of temporary classification a lot more.