Hello, I am attempting an upgrade from: - Trac 1.2.2 - CentOS 6.10 - Python 2.7.5
To: - Trac 1.2.6 - CentOS 7.9 - Python 2.7.5 After importing all our Trac data, the site seems perfectly functional minus one major detail. We are unable to reassign tickets, despite no configuration change within trac.ini. Screenshots below of what we expect to see (prod) vs what we see now (test). Also relevant information from our trac.ini in regards to the reassignment configuration, which again, is unchanged from production. All users who have attempted this have the proper TICKET_MODIFY permissions or even have higher permissions. It still will not show up even if explicit TICKET_MODIFY permissions are set or if we are explicit in the workflow instead of the wildcards. I do see in the logs what I assume is an attempt to render the reassign option: Trac[default_workflow] DEBUG: render_ticket_action_control: action "reassign" Please let me know if I need to provide more information. Thanks!! # Correct [image: trac_prod_right.png] # Incorrect [image: trac-test_wrong.png] # trac.ini information: [ticket] ... # instead of an open text box, populate the owner list with a drop-down restrict_owner = enabled # Which workflow plugin to use, this is default with Trac workflow = ConfigurableTicketWorkflow ... [ticket-workflow] ... # From any ticket state to any other ticket state reassign= * -> * # Custom prompt that appears reassign.name = Reassign Owner # Trac action to perform reassign.operations = set_owner # Trac permissions required to do this action. reassign.permissions = TICKET_MODIFY -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/f7924dbe-743e-46f1-921d-33ff8cae0e7fn%40googlegroups.com.
