wiki:TracQuery
Last modified 14 years ago

Trac Ticket Queries

Table of Contents

In addition to reports, Trac provides support for custom ticket queries, used to display lists of tickets meeting a specified set of criteria.

To configure and execute a custom query, switch to the View Tickets module from the navigation bar, and select the Custom Query link.

Filters

When you first go to the query page the default filter will display tickets relevant to you:

  • If logged in then all open tickets it will display open tickets assigned to you.
  • If not logged in but you have specified a name or email address in the preferences then it will display all open tickets where your email (or name if email not defined) is in the CC list.
  • If not logged and no name/email defined in the preferences then all open issues are displayed.

Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right). Filters with either a text box or a pulldown menu of options can be added multiple times to perform an or of the criteria.

You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

Once you've edited your filters click the Update button to refresh your results.

Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the Next Ticket or Previous Ticket links just below the main menu bar, or click the Back to Query link to return to the query page.

You can safely edit any of the tickets and continue to navigate through the results using the Next/Previous/Back to Query links after saving your results. When you return to the query any tickets which were edited will be displayed with italicized text. If one of the tickets was edited such that it no longer matches the query criteria the text will also be greyed. Lastly, if a new ticket matching the query criteria has been created, it will be shown in bold.

The query results can be refreshed and cleared of these status indicators by clicking the Update button again.

Saving Queries

Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have Updated the view and then click the Save query button displayed beneath the results. You can also save references to queries in Wiki content, as described below.

Note: one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click Save query. This will build the query string for you. All you need to do is remove the extra line breaks.

You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page. 

[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

Which is displayed as:

Active tickets against 1.0

This uses a very simple query language to specify the criteria (see Query Language).

Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading ? character: 

[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

Which is displayed as:

Assigned tickets by owner

Using the [[TicketQuery]] Macro

The  TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.

Example: 

[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

This is displayed as:

No results

Just like the query: wiki links, the parameter of this macro expects a query string formatted according to the rules of the simple ticket query language.

A more compact representation without the ticket summaries is also available: 

[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

This is displayed as:

No results

Finally, if you wish to receive only the number of defects that match the query, use the count parameter. 

[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

This is displayed as:

0

Customizing the table format

You can also customize the columns displayed in the table format (format=table) by using col=<field> - you can specify multiple fields and what order they are displayed by placing pipes (|) between the columns like below: 

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 46)

Ticket Resolution Summary Owner Reporter
#74 fixed 聚超值一个方法的优化 chenchongqi
#73 fixed 第二次代码检查 lifeng
#72 fixed 汽车网评论发动态引起性能问题总结 chenyang

Full rows

In table format you can also have full rows by using rows=<field> like below: 

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 46)

Ticket Resolution Summary Owner Reporter
#74 fixed 聚超值一个方法的优化 chenchongqi

Reported by chenchongqi, 13 years ago.
Description

前几天在 代码审核过程中发现了一段比较有代表性的代码，于是动手分拆了一下并跟大家分享整个优化的过程。

首先我们看一下原来的代码： 

/**
 * 根据分类分页获取爆料列表
 * 
 * @param pageNo
 * @param pageSize
 * @param categoryId
 * @return
 */
public List<Topic> getIndexPageByCategoryId( int pageNo, int pageSize, long categoryId ) {
        List<Topic> list = new ArrayList<Topic>();
        StringBuilder sql = new StringBuilder();
        if( categoryId != 0 ) {
                sql.append( "SELECT DISTINCT a.topicId FROM pcbest_topic a,pcbest_topic_type_relation b," );
                sql.append( " ( SELECT typeid FROM pcbest_topic_type c WHERE parentid=? UNION ALL SELECT ? ) type_all " );
                sql.append( " WHERE a.auditStatus=? AND a.topicId  = b.`topicId` AND b.`topicTypeId` = type_all.typeId");
                sql.append( " AND a.recommendIndex=?" );
                sql.append( " ORDER BY a.top DESC,a.auditAt DESC " );
                List<Topic> topicList = this.listTopicPage( sql.toString(), pageNo, pageSize, categoryId, categoryId, Topic.AUDIT_STATUS_SUCCESS, Topic.RECOMMEND_INDEX_YES );
                list.addAll( topicList );
        }
        else {
                sql.append( "select topicId from pcbest_topic where auditStatus=?" );
                sql.append( " AND recommendIndex=? and seq=0" );
                sql.append( " ORDER BY top DESC,auditAt DESC " );
                List<Topic> topicList = this.listTopicPage( sql.toString(), pageNo, pageSize, Topic.AUDIT_STATUS_SUCCESS, Topic.RECOMMEND_INDEX_YES );
                list.addAll( topicList );
        }

        if( pageNo == 1 && categoryId == 0 ) {
                sql = new StringBuilder();
                sql.append( "select topicId from pcbest_topic where auditStatus=1" );
                sql.append( " AND recommendIndex=1 AND seq > 0" );
                sql.append( " ORDER BY seq asc" );
                List<Topic> adList = geliDao.list( Topic.class, sql.toString() );
                for( Topic topic : adList ) {
                        int len = list.size();
                        int seq = topic.getSeq();
                        if( seq > len ) {
                                list.add( topic );
                        }
                        else {
                                seq--;
                                list.add( seq, topic );
                        }
                        len++;
                }
        }
        return list;
}

这里面有几个问题：

  • 明明是叫getIndexPageByCategoryId，但是里面又分叉出categoryId=0的流程
  • 明明参数是按页查询，但是里面又分叉出pageNo=1的流程
  • 里面还隐藏了一个categoryId=0 && pageNo=1的流程

从这几个点看很明显里面是揉合了太多的业务，让我们来拆分一下吧，具体思路是：

  • 一种是nomal无参数查询的，正常分页
  • 一种是用categoryId做参数查询的，正常分页
  • 一种是无参数查询所有带指定顺序的广告，无分页
  • 最后一种其实是个无参数的排行榜，综合了广告

这样前三种是基础服务，最后一种是在基础服务上包装的综合服务，其实拆分后如果还有其他综合服务就很容易在基础服务上灵活组装和扩展，那我们就按这个思路来分拆如下： 

	/**
	 * 获取无参数爆料列表
	 * 
	 * @param pageNo
	 * @param pageSize
	 * @return
	 */
	public List<Topic> getIndexPageNormal( int pageNo, int pageSize) {
		StringBuilder sql = new StringBuilder();

                sql.append( "select topicId from pcbest_topic where auditStatus=?" );
                sql.append( " AND recommendIndex=? and seq=0" );
                sql.append( " ORDER BY top DESC,auditAt DESC " );
                List<Topic> topicList = this.listTopicPage( sql.toString(), pageNo, pageSize, Topic.AUDIT_STATUS_SUCCESS, Topic.RECOMMEND_INDEX_YES );
		return topicList;
	}

	/**
	 * 根据分类分页获取爆料列表
	 * 
	 * @param pageNo
	 * @param pageSize
	 * @param categoryId
	 * @return
	 */
	public List<Topic> getIndexPageByCategoryId( int pageNo, int pageSize, long categoryId ) {
		List<Topic> list = new ArrayList<Topic>();
		StringBuilder sql = new StringBuilder();

                sql.append( "SELECT DISTINCT a.topicId FROM pcbest_topic a,pcbest_topic_type_relation b," );
                sql.append( " ( SELECT typeid FROM pcbest_topic_type c WHERE parentid=? UNION ALL SELECT ? ) type_all " );
                sql.append( " WHERE a.auditStatus=? AND a.topicId  = b.`topicId` AND b.`topicTypeId` = type_all.typeId");
                sql.append( " AND a.recommendIndex=?" );
                sql.append( " ORDER BY a.top DESC,a.auditAt DESC " );
                list = this.listTopicPage( sql.toString(), pageNo, pageSize, categoryId, categoryId, Topic.AUDIT_STATUS_SUCCESS, Topic.RECOMMEND_INDEX_YES );
		
		return list;
	}

	/**
	 * 获取全部指定排位的广告爆料列表
	 * 
	 * @return
	 */
        public List<Topic> getAdIndexList(){            
            StringBuilder sql = new StringBuilder();
            sql = new StringBuilder();
            sql.append( "select topicId from pcbest_topic where auditStatus=1" );
            sql.append( " AND recommendIndex=1 AND seq > 0" );
            sql.append( " ORDER BY seq asc" );
            List<Topic> adList = geliDao.list( Topic.class, sql.toString());
            return adList;
        }

	/**
	 * 综合广告的排行榜爆料列表
	 * 
	 * @param maxTop
	 * @return
	 */
	public List<Topic> getIndexTop( int maxTop) {

            List<Topic> adList = getAdIndexList();
            List<Topic> list = getIndexPageNormal(1, maxTop);

            for( Topic topic : adList ) {
                    int len = list.size();
                    int seq = topic.getSeq();
                    if( seq > len ) {
                            list.add( topic );
                    }
                    else {
                            seq--;
                            list.add( seq, topic );
                    }
                    len++;
            }                 
            return list;
	}

怎么样，是不是清爽了很多咧？

#73 fixed 第二次代码检查 lifeng

Reported by lifeng, 13 years ago.
Description

1、代码检查的项目：电脑网的下载和直播2个应用

2、主要检查对象：绑定变量的SQL写法

3、参与人员

汽车组：梁勤升 电脑组：成荣伟 女性组：邱龙根 游戏/亲子/家居：叶炜贤 通用平台：曾杰 论坛互动：秦鸿源

分组情况： 梁勤升 邱龙根 成荣伟 秦鸿源 叶炜贤 曾杰

4、检查方式和检查工具： （1）使用QA提供的工具从SVN提取出2013年1月1日之后有变更的代码； （2）采取2人结对的方式共同检查同样的代码； （3）检查总结，出报告；

5、工作安排： （1）2013.07.01 - 2013.07.08 结对检查； （2）2013.07.10 汇总检查结果； （2）2013.07.15 出检查报告；

#72 fixed 汽车网评论发动态引起性能问题总结 chenyang

Reported by chenyang, 13 years ago.
Description

在开发评论系统回复评论发消息功能时，发现使用的uc-client.jar是较旧的版本，最后更换了ucClient1.1.jar.使用旧版本的包与个人中心系统通信会出错。结果导致发动态不成功。代码如下: 

HttpClient httpClient = new HttpClient();
			if (bbsUseProxy){
				HostConfiguration hc = new HostConfiguration();
			    hc.setProxy(ucProxyServer, ucProxyPort);
			    httpClient.setHostConfiguration(hc);
			    httpClient.getState().setProxyCredentials(AuthScope.ANY,new UsernamePasswordCredentials(ucProxyUser,ucProxyPass));	      
			}


//发动态      		
			if(Constants.SETTING_PCGAMES.equalsIgnoreCase(webSite)){
				Map<String,Object> nf = new HashMap<String,Object>();
				nf.put("accountId", longUserId);
				nf.put("resource", "<a href='"+comment.getTopic().getUrl()+"' target='_blank'>"+comment.getTopic().getTitle()+"</a>");
				boolean isOK =  ucClient.newsfeed(longUserId, 3040, nf);
			}
    		else {
		    	Map<String,Object> contents = new HashMap<String,Object>();
		    	contents.put("content", "<a href='"+comment.getTopic().getUrl()+"' target='_blank'>"+comment.getTopic().getTitle()+"</a>");
		    	ucClient.newsfeed(longUserId, 17, contents);

//加积分
httpClient.getParams().setParameter("http.protocol.content-charset", "gbk");
	    	httpClient.getParams().setSoTimeout(timeout);
	    	cn.pconline.bbs6.client.BbsClient bbsClient = new cn.pconline.bbs6.client.BbsClient();
	    	bbsClient.setHttpClient(httpClient);
	    	bbsClient.setBbsServer(bbsServer);
	    	long scoreCh = bbsClient.changeScore(longUserId, 1, "cmt4al", "create cmt", "发表文章评论加分");

旧包导致发动态代码出错，导致httpclient没有释放,最后，连接耗尽。。。 修改后代码如下： 

 //发动态      		
			if(Constants.SETTING_PCGAMES.equalsIgnoreCase(webSite)){
				final Map<String,Object> nf = new HashMap<String,Object>();
				nf.put("accountId", longUserId);
				nf.put("resource", "<a href='"+comment.getTopic().getUrl()+"' target='_blank'>"+comment.getTopic().getTitle()+"</a>");
				
				Executor.Instance.execute(new Runnable(){
					@Override
					public void run() {
						ucClient.newsfeed(uid, 3040, nf);
					}
				});
			}
    		else {
		    	final Map<String,Object> contents = new HashMap<String,Object>();
		    	contents.put("content", "我评论了文章\"<a href='"+comment.getTopic().getUrl()+"' target='_blank'>"+comment.getTopic().getTitle()+"</a>\"");
		    	Executor.Instance.execute(new Runnable(){
					@Override
					public void run() {
						ucClient.newsfeed(uid, 2032, contents);
					}
		    	});
    		}
	    	//发积分
			HttpClient httpClient = new HttpClient();
			if (bbsUseProxy){
				HostConfiguration hc = new HostConfiguration();
			    hc.setProxy(ucProxyServer, ucProxyPort);
			    httpClient.setHostConfiguration(hc);
			    httpClient.getState().setProxyCredentials(AuthScope.ANY,new UsernamePasswordCredentials(ucProxyUser,ucProxyPass));	      
			}
			httpClient.getParams().setParameter("http.protocol.content-charset", "gbk");
	    	httpClient.getParams().setSoTimeout(timeout);
	    	final cn.pconline.bbs6.client.BbsClient bbsClient = new cn.pconline.bbs6.client.BbsClient();
	    	bbsClient.setHttpClient(httpClient);
	    	bbsClient.setBbsServer(bbsServer);
	    	
	    	Executor.Instance.execute(new Runnable(){
				@Override
				public void run() {
					try{
						bbsClient.changeScore(uid, 1, "cmt4al", "create cmt", "发表文章评论加分");
					}catch(Exception uce){
						log.error("发表文章评论加分出错:"+uce);
						uce.printStackTrace();
					}
				}
	    		
	    	});

修改后，上线观察，一切正常

Query Language

query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (&). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (|), meaning that the filter matches any of the values. To include a literal & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches one of the values
~= the field content contains one or more of the values
^= the field content starts with one of the values
$= the field content ends with one of the values

All of these operators can also be negated:

!= the field content matches none of the values
!~= the field content does not contain any of the values
!^= the field content does not start with any of the values
!$= the field content does not end with any of the values

The date fields created and modified can be constrained by using the = operator and specifying a value containing two dates separated by two dots (..). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be left out to avoid having to quote the query string.

created=2007-01-01..2008-01-01 query tickets created in 2007
created=lastmonth..thismonth query tickets created during the previous month
modified=1weekago.. query tickets that have been modified in the last week
modified=..30daysago query tickets that have been inactive for the last 30 days

See also: TracTickets, TracReports, TracGuide