| Title | Can't restrict State field values by TeamTrack project |
| Status | duplicate |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | The P4DTI generates a jobspec for Perforce. In the TeamTrack integration, this jobspec includes a 'State' field, replicated from the STATE field of a TeamTrack issue. This 'State' field is a 'select' field. The allowable values for this field are derived from the complete set of possible STATEs of issues in any TeamTrack project. This includes the STATEs of issues in projects which are not replicated (i.e. which are restricted from replication using the replicate_p configuration parameter). Users would like [1] to be able to exclude STATEs from non-replicated projects, but cannot do so at present. |
| Analysis | This is a duplicate of job000231. The allowable values for the 'State' field, and the translation mapping of this field between Perforce and TeamTrack, are computed in make_state_pairs() in configure_teamtrack.py. We would have to add some sort of configuration parameter and restrict the query used to obtain the state values. The current query is 'TS_PROJECTID IN (SELECT TS_ID FROM TS_WORKFLOWS WHERE TS_TABLEID = case_table_id)'. We could use a parameter called something like replicated_projects and also use the same parameter to do a first cut for the replicate_p test. |
| How found | customer |
| Evidence | [1] <http://info.ravenbrook.com/mail/2002/11/22/16-56-52/0.txt> |
| Observed in | 1.5.0 |
| Introduced in | 0.3.0 |
| Created by | Nick Barnes |
| Created on | 2002-11-22 16:57:19 |
| Last modified by | Gareth Rees |
| Last modified on | 2002-11-25 12:28:52 |
| History | 2002-11-22 NB Created. 2002-11-25 GDR This is a duplicate of job000231. |