P4DTI issue job000232

TitleLog and e-mail messages are confusing if jobname is different from the issue name
Statusclosed
Priorityoptional
Assigned userGareth Rees
OrganizationRavenbrook
DescriptionLog messages and e-mail messages describe an issue using the name of the corresponding job. This is OK when they are the same (which is the usual case), but misleading when they are not (which could happen if you've migrated your jobs and kept the jobname).
AnalysisThis is because we use readable_name to get a readable name for the job, even though that returns the name of the corresponding job. I suggest having two methods readable_name and corresponding_id and using them appropriately.
How foundmanual_test
EvidenceDiscovered while testing migration
Observed in1.0.0
Created byGareth Rees
Created on2001-02-23 12:12:14
Last modified byGareth Rees
Last modified on2001-12-10 19:26:25
History2001-02-23 GDR Created.

Fixes

Change Effect Date User Description
8976 closed 2001-02-23 12:47:31 Gareth Rees Added corresponding_id method defect_tracker_issue class and changed the definition of readable_name, so that issue names are reported properly even if they differ from the corresponding jobname.