[Trac-dev] mastertickets: closing tickets with blockers

[Greg Troxel]

With

trac-1.0.5 Repository browser, wiki, and issue tracking system
trac-plugins-MasterTickets-3.0.4.12946 Ticket dependency plugin for Trac

I tried to close a ticket A that had a blocking open ticket B. I got a
page with a warning about B, and showing A as closed. But asking for
the A page again shows it open.

So I think something's wrong in how the mastertickets can-close hook
stops the closing but not the rendering of the ticket as closed.

[RjOllos]

Post by Greg Troxel
With
trac-1.0.5 Repository browser, wiki, and issue tracking system
trac-plugins-MasterTickets-3.0.4.12946 Ticket dependency plugin for Trac
I tried to close a ticket A that had a blocking open ticket B. I got a
page with a warning about B, and showing A as closed. But asking for
the A page again shows it open.
So I think something's wrong in how the mastertickets can-close hook
stops the closing but not the rendering of the ticket as closed.

The plugin is in pretty bad shape and I haven't had time to fix it. When I
find time I'm also more inclined to spend time backporting Bloodhound
TicketRelationsPlugin to Trac, which is a more generalized replacement for
MasterTicketsPlugin (and SubticketsPlugin).

The major task for MasterTicketsPlugin is to modify the database
transactions to be atomic, so that the database cannot get into an
inconsistent state. The situation you describe sounds similar to some of
the open tickets I've read through in the past. You might have some success
upgrading to 4.0dev and manually fixing your database.

For future reference, user issues should be directed to the trac-users
mailing list:
http://trac.edgewall.org/wiki/MailingList

- Ryan

[RjOllos]

Post by RjOllos

Post by Greg Troxel
With
trac-1.0.5 Repository browser, wiki, and issue tracking system
trac-plugins-MasterTickets-3.0.4.12946 Ticket dependency plugin for Trac
I tried to close a ticket A that had a blocking open ticket B. I got a
page with a warning about B, and showing A as closed. But asking for
the A page again shows it open.
So I think something's wrong in how the mastertickets can-close hook
stops the closing but not the rendering of the ticket as closed.

The plugin is in pretty bad shape and I haven't had time to fix it. When I
find time I'm also more inclined to spend time backporting Bloodhound
TicketRelationsPlugin to Trac, which is a more generalized replacement for
MasterTicketsPlugin (and SubticketsPlugin).
The major task for MasterTicketsPlugin is to modify the database
transactions to be atomic, so that the database cannot get into an
inconsistent state. The situation you describe sounds similar to some of
the open tickets I've read through in the past. You might have some success
upgrading to 4.0dev and manually fixing your database.
For future reference, user issues should be directed to the trac-users
http://trac.edgewall.org/wiki/MailingList
- Ryan

There's a 4.0.0dev for MasterTicketsPlugin that is compatible with Trac
1.0+. I'll create the release as soon as there is sufficient feedback.

- Ryan

[RjOllos]

Post by RjOllos

Post by RjOllos

Post by Greg Troxel
With
trac-1.0.5 Repository browser, wiki, and issue tracking system
trac-plugins-MasterTickets-3.0.4.12946 Ticket dependency plugin for Trac
I tried to close a ticket A that had a blocking open ticket B. I got a
page with a warning about B, and showing A as closed. But asking for
the A page again shows it open.
So I think something's wrong in how the mastertickets can-close hook
stops the closing but not the rendering of the ticket as closed.

The plugin is in pretty bad shape and I haven't had time to fix it. When
I find time I'm also more inclined to spend time backporting Bloodhound
TicketRelationsPlugin to Trac, which is a more generalized replacement for
MasterTicketsPlugin (and SubticketsPlugin).
The major task for MasterTicketsPlugin is to modify the database
transactions to be atomic, so that the database cannot get into an
inconsistent state. The situation you describe sounds similar to some of
the open tickets I've read through in the past. You might have some success
upgrading to 4.0dev and manually fixing your database.
For future reference, user issues should be directed to the trac-users
http://trac.edgewall.org/wiki/MailingList
- Ryan

There's a 4.0.0dev for MasterTicketsPlugin that is compatible with Trac
1.0+. I'll create the release as soon as there is sufficient feedback.
- Ryan

There's a 4.0.0 release of MasterTickets, available on trac-hacks.org and
PyPI:
* https://trac-hacks.org/svn/masterticketsplugin/tags/mastertickets-4.0.0/
* https://pypi.python.org/pypi/TracMasterTickets/4.0.0

I haven't gone through the whole backlog of issues, but a significant
number should be fixed now.

- Ryan