Hi Julie,
Here is the use case for this idea.
All Eng specific features are prefixed with ‘ENG:’ to help PMs know these are infra or compliance features. So PM’s do not want to import these features to Aha. use do not have access to all fields on Rally and are not familiar with usage, they would not want to update Rally records.
When PMs try to import ideas, typically, they would filter on ‘status’ or a ‘release’.
The Rally import basically brings all records that meet the criteria.
1. When it shows the records, it shows the count which also include already imported features which is somewhat misleading until the PM’s realize that the number includes the already imported ones. (It would be helpful if some text can be included to indicate that on the import screen)
2. When you click on ‘import’ instead of importing all records, it lists the feature name & reference id of all the valid records (not including already imported) with a check box, then the PM will have the option to select the records that they would like to import. This will help PM’s to exclude all the ‘ENG’ records
To clarify, are you referring to the Workspace settings > Import from development tool page?
Currently, you can add a Rally grid query string to filter the records before the import screen.
Curious, can you please share more about your use case? Are you just looking for a way to manually pick and choose records that don't necessarily align with a common search query?
Thank you for sharing details around your use case, Jyothiim! It definitely makes sense.
We will continue to monitor this idea for community feedback.
Hi Julie,
Here is the use case for this idea.
All Eng specific features are prefixed with ‘ENG:’ to help PMs know these are infra or compliance features. So PM’s do not want to import these features to Aha. use do not have access to all fields on Rally and are not familiar with usage, they would not want to update Rally records.
When PMs try to import ideas, typically, they would filter on ‘status’ or a ‘release’.
The Rally import basically brings all records that meet the criteria.
1. When it shows the records, it shows the count which also include already imported features which is somewhat misleading until the PM’s realize that the number includes the already imported ones. (It would be helpful if some text can be included to indicate that on the import screen)
2. When you click on ‘import’ instead of importing all records, it lists the feature name & reference id of all the valid records (not including already imported) with a check box, then the PM will have the option to select the records that they would like to import. This will help PM’s to exclude all the ‘ENG’ records
Regards,
Jyothiim
Thanks for the idea!
To clarify, are you referring to the Workspace settings > Import from development tool page?
Currently, you can add a Rally grid query string to filter the records before the import screen.
Curious, can you please share more about your use case? Are you just looking for a way to manually pick and choose records that don't necessarily align with a common search query?