New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #16573 (closed defect: invalid)

Opened 5 years ago

Last modified 4 years ago

can't re-open my own ticket

Reported by: macosforge.org@… Owned by: wsiegrist@…
Priority: Normal Milestone:
Component: server/hosting Version:
Keywords: Cc:
Port:

Description

i opened bug # 11420. i'd like to re-open it, but i get an error saying i don't have permission. perhaps trac gets confused by the fact that i changed my email address along the way?

Change History

comment:1 follow-up: ↓ 9 Changed 5 years ago by wsiegrist@…

  • Status changed from new to closed
  • Resolution set to invalid

Open a new ticket and note that they are related.

comment:2 Changed 5 years ago by macosforge.org@…

that completely defeats half the purpose of using a ticketing system. are you really seriously saying that having multiple tickets opened on the same issue is better that reopening an existing ticket that was prematurely closed? if so, that is contrary to the way the admins of EVERY other bugtracking system i use feel :(

comment:3 Changed 5 years ago by macosforge.org@…

ping

comment:4 follow-up: ↓ 6 Changed 5 years ago by raimue@…

As far as I know you would need the TICKET_MODIFY permission to reopen a ticket. But this gives full control about the ticket regarding description, reporter etc. We don't want everyone to edit that.

Instead of opening new tickets, you can still add a comment and ask for reopen.

comment:5 Changed 5 years ago by blb@…

Now that we use trac 0.11, can't we use the TracWorkflow stuff to make this work without TICKET_MODIFY (eg, TICKET_CREATE for reopened)? Or is trac.ini offlimits?

comment:6 in reply to: ↑ 4 ; follow-up: ↓ 7 Changed 4 years ago by macosforge.org@…

Replying to raimue@…:

Instead of opening new tickets, you can still add a comment and ask for reopen.

unfortunately, that system has been proven to not be robust :(

please reopen this ticket :P

comment:7 in reply to: ↑ 6 Changed 4 years ago by raimue@…

Replying to macosforge.org@…:

please reopen this ticket :P

Which one? #16573 or #11420?

comment:8 Changed 4 years ago by macosforge.org@…

i meant #16573, but i'd like #11420 reopened as well.

thanks!

marc

comment:9 in reply to: ↑ 1 Changed 4 years ago by blb@…

Replying to wsiegrist@…:

Open a new ticket and note that they are related.

Is that the official MacOSForge trac policy, or is there anything like what I asked in comment 5?

comment:10 Changed 4 years ago by macosforge.org@…

could this ticket (#16573) please be reopened?

comment:11 Changed 4 years ago by anonymous

  • Milestone Website & Documentation deleted

Milestone Website & Documentation deleted

comment:12 Changed 4 years ago by macosforge.org@…

ping

comment:13 Changed 4 years ago by macosforge.org@…

raimue: do you now see why being able to reopen one's own tickets is important? it's been 6 months that i've been asking for this ticket to be reopened and it still hasn't been :(

Note: See TracTickets for help on using tickets.