Missing reassign button on Trac 1.2.6

[Tyler]

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

# Incorrect

# 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

[RjOllos]

We had to make a change to correct a bug. Please change:

- reassign.operations = set_owner

+ reassign.operations = set_owner, leave_status 

https://trac.edgewall.org/wiki/1.3/TracWorkflow?action=diff&version=4&old_version=2#

Ryan

[Tyler Boswick - NOAA Affiliate]

Wow, that actually worked.  Thanks for the help and I'm glad it was simple!

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/696a24e5-da44-4e48-990a-1004b35323d8n%40googlegroups.com.

--

Tyler Boswick
Infrastructure, Slurm, & HPC Systems Administrator (NOAA Affiliate)
RedLine Performance Solutions LLC
Princeton University Forrestal Campus
201 Forrestal Road
Princeton, NJ 08540

P. (609) 452-5828

[Ryan Ollos]

On Tue, Feb 2, 2021 at 10:01 AM 'Tyler Boswick - NOAA Affiliate' via Trac Users <trac-...@googlegroups.com> wrote:

Wow, that actually worked.  Thanks for the help and I'm glad it was simple!

Good to hear. On our end, it's a good reminder to document that issue. It was unfortunate we had to make that change, but it should have never worked without the "leave_status" to begin with, and the correction was needed to fix some other issues.

Ryan 

[RjOllos]

Edited the TracUpgrade pages as described in:

https://trac.edgewall.org/ticket/13087#comment:10

Ryan