Does EWM requirements configuration use the current global configuration context for the selection dialog?
When attempting to create a link from an EWM work item to a DOORS Next requirement in a config enabled context, I am getting errors saying the selected requirement is not consistent with the configuration context.
The EWM configuration is set to a global configuration that includes DNG contribution
The EWM release for the work item planed for is associated with the same global configuration.
I can create a link from the DOORS Next requirement to the EWM Work Item. But there appears to be a bug in EWM where the requirement selection dialog is not using the configuration context when creating a link.
https://trs-filter.smartfacts.com/rm/resources/TX_BlXJoBJdEfGwzfpcs3AZcA link created from EWM to DNG
https://trs-filter.smartfacts.com/rm/resources/TX_BpXf4BJdEfGwzfpcs3AZcA?oslc_config.context=https%3A%2F%2Ftrs-filter.smartfacts.com%2Fgc%2Fconfiguration%2F4 Link in EWM created from DNG.
When creating the link from EWM to DOORS Next, the oslc_config.context parameter is not being included in the link, which would seem to imply that the EWM requirement picker is not using the EWM configuration context.