Edgewall Software
Modify

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#12644 closed defect (worksforme)

BatchModify Ticket no longer available in 1.2

Reported by: kratky@… Owned by:
Priority: normal Milestone:
Component: ticket system Version: 1.2
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:

Description

After upgrading to 1.2 from 1.0, the Batch Modify functionality seems to be gone on the ticket report result page generated by a ticket report. All affected users have the TICKET_BATCH_MODIFY permission.

Attachments (2)

Screen Shot 2016-12-21 at 08.03.08.png (29.3 KB ) - added by Ryan J Ollos 3 years ago.
query_log (9.6 KB ) - added by Ryan J Ollos 3 years ago.

Download all attachments as: .zip

Change History (8)

by Ryan J Ollos, 3 years ago

comment:1 by Ryan J Ollos, 3 years ago

Milestone: 1.2.1

This is an InstallationIssue, which should be directed to the MailingList.

However, let's check a few things.

  • Trac 1.0 added batch modify capability. Make sure you don't have BatchModifyPlugin installed.
  • Check the plugins admin page (/admin/plugins). Is the component enabled?
  • check the logs

comment:2 by anonymous, 3 years ago

Batch Modify Plugin is not installed and Batch Modify Component is enabled.

Upon generation a report I get the following messages in the log:

2016-12-21 17:23:11,622 Trac[perm] DEBUG: No policy allowed anonymous performing SEARCH_VIEW on None
2016-12-21 17:23:11,624 Trac[main] DEBUG: Negotiated locale: None -> en_US
2016-12-21 17:23:11,631 Trac[chrome] DEBUG: Prepare chrome data for request
2016-12-21 17:23:11,632 Trac[perm] DEBUG: No policy allowed anonymous performing XML_RPC on None
2016-12-21 17:23:11,632 Trac[perm] DEBUG: No policy allowed anonymous performing ROADMAP_VIEW on None
2016-12-21 17:23:11,632 Trac[perm] DEBUG: No policy allowed anonymous performing TICKET_VIEW on <Resource 'ticket'>
2016-12-21 17:23:11,632 Trac[perm] DEBUG: No policy allowed anonymous performing TICKET_CREATE on None
2016-12-21 17:23:11,633 Trac[perm] DEBUG: No policy allowed anonymous performing TRAC_ADMIN on <Resource u'admin:general/basics'>
2016-12-21 17:23:11,633 Trac[perm] DEBUG: No policy allowed anonymous performing TRAC_ADMIN on <Resource u'admin:general/logging'>
2016-12-21 17:23:11,633 Trac[perm] DEBUG: No policy allowed anonymous performing PERMISSION_GRANT on <Resource u'admin:general/perm'>
2016-12-21 17:23:11,633 Trac[perm] DEBUG: No policy allowed anonymous performing PERMISSION_REVOKE on <Resource u'admin:general/perm'>
2016-12-21 17:23:11,634 Trac[perm] DEBUG: No policy allowed anonymous performing TRAC_ADMIN on <Resource u'admin:general/plugin'>
2016-12-21 17:23:11,634 Trac[perm] DEBUG: No policy allowed anonymous performing TICKET_ADMIN on <Resource u'admin:ticket/components'>
2016-12-21 17:23:11,634 Trac[perm] DEBUG: No policy allowed anonymous performing TICKET_ADMIN on <Resource u'admin:ticket/milestones'>
2016-12-21 17:23:11,635 Trac[perm] DEBUG: No policy allowed anonymous performing TICKET_ADMIN on <Resource u'admin:ticket/versions'>
2016-12-21 17:23:11,635 Trac[perm] DEBUG: No policy allowed anonymous performing TICKET_ADMIN on <Resource u'admin:ticket/priority'>
2016-12-21 17:23:11,635 Trac[perm] DEBUG: No policy allowed anonymous performing TICKET_ADMIN on <Resource u'admin:ticket/resolution'>
2016-12-21 17:23:11,635 Trac[perm] DEBUG: No policy allowed anonymous performing TICKET_ADMIN on <Resource u'admin:ticket/severity'>
2016-12-21 17:23:11,636 Trac[perm] DEBUG: No policy allowed anonymous performing TICKET_ADMIN on <Resource u'admin:ticket/type'>
2016-12-21 17:23:11,636 Trac[perm] DEBUG: No policy allowed anonymous performing VERSIONCONTROL_ADMIN on <Resource u'admin:versioncontrol/repository'>
2016-12-21 17:23:11,636 Trac[perm] DEBUG: No policy allowed anonymous performing TAGS_ADMIN on None
2016-12-21 17:23:11,637 Trac[perm] DEBUG: No policy allowed anonymous performing REPORT_VIEW on <Resource u'report:-1'>
2016-12-21 17:23:11,637 Trac[perm] DEBUG: No policy allowed anonymous performing TIMELINE_VIEW on <Resource 'timeline'>
2016-12-21 17:23:11,641 Trac[perm] DEBUG: No policy allowed anonymous performing BROWSER_VIEW on <Resource u'repository:refactory, source:/'>
2016-12-21 17:23:11,642 Trac[perm] DEBUG: No policy allowed anonymous performing WIKI_VIEW on <Resource u'wiki:WikiStart'>
2016-12-21 17:23:11,642 Trac[perm] DEBUG: No policy allowed anonymous performing WIKI_VIEW on <Resource u'wiki:TracGuide'>
2016-12-21 17:23:11,642 Trac[perm] DEBUG: No policy allowed anonymous performing TAGS_VIEW on None
2016-12-21 17:23:11,643 Trac[main] WARNING: [192.168.200.1] HTTPForbidden: 403 Forbidden (SEARCH_VIEW privileges are required to perform this operation. You don't have the required permissions.)

My account does have the SEARCH_VIEW permission.

comment:3 by Ryan J Ollos, 3 years ago

Note the Batch Modify functionality only appears on Query pages (/query), not Reports (/report). When navigating to the /query page, you should get log output like show in query_log.

The output in comment:2 is for a non-authenticated user, and appears to be a navigation to /search.

It would also be useful to see the output of trac-admin $env permission list.

by Ryan J Ollos, 3 years ago

Attachment: query_log added

comment:4 by anonymous, 3 years ago

Resolution: fixed
Status: newclosed

My bad. I have found the batch modify feature on the query page. It would be helpful if the sentence

Note the Batch Modify functionality only appears on Query pages (/query), not Reports (/report).

could be added to the TracBatchModify wiki page.

comment:5 by figaro, 3 years ago

That page is part of a wiki and you are welcome to add this yourself, together with any other findings you may have observed.

in reply to:  4 comment:6 by Jun Omae, 3 years ago

Resolution: fixedworksforme

Replying to anonymous:

could be added to the TracBatchModify wiki page.

TracBatchModify says:

Trac supports modifying a batch of tickets in one request from custom query results.

That is already documented.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.