We use an external system to issue Request For Change approvals - each RFC becomes a Project in JIRA, or other systems. Global reporting is based on intersecting and RFC number with a Sprint within a system. I would like to be able to record the corresponding RFC id with the creation of the JIRA project (key) such that every Issue Type created and run for that project would carry or roll up to that ID and could be intersected with another data point such as Sprint. I need this for external reporting aggregate. For example, our RFC system Issues an ID of RFC1000, a project is created in JIRA called Investments and Inquiries - Key INVMT. Ideally, every Test Case, Execution, Run, Status, Plan, would be traceable by the RFC1000 ID. So an outside engine could ask for Project filed x = RFC1000, Sprint = 1, give me Test Execution Statuses.
I hope that makes some sense, but is it possible and if so, how/where would the RFC number be stored?
Thanks,
Rob.
Hi Rob,
Since Tests, Pre-Conditions, Test Sets, Test Executions and Test Plans are issue types, you may add custom fields to them as means to add additional information. Thus, you may add an "RFC ID" custom field to them if you want.
Concerning Test Runs, since they are not issues, and while we don't have parameters at the Test Run level, you may add that reference in the comments (i..e in the global comment) of the Test Run.
In your case you may decide to add that RFC ID just on some of the entities; if you're working using Sprints, you may just add the RFC ID to the user stories and somehow they will be implicitly affecting the related entities (in other words, you may always come to the requirement to see the RFC ID from a Test, or from a Test inside a Test Set/Test Execution/Test Plan).
Best regards,
Xray Team
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.