Investigate why issue condition uses "global scope" for composite lookups in an if/else block

Description

When using an issue condition on a project rule, the list of available composite values will be based on the project’s values.

 

However, if you put that above issue condition in a if/else block then it uses the global values/suggestions API. From the looks of things we may have an issue passing the projectId somewhere?

Environment

None

Activity

Show:
Yvan Martin (CB)
June 28, 2019, 6:51 AM

this.props.ruleProject.id does not exist in the if/else block render. Instead it looks like we can usethis.props.context.projectId which appears to be available in both cases.

Yvan Martin (CB)
June 28, 2019, 6:58 AM

I’ve pushed to the branch AUT-1555-project-id with this change, but it needs more testing/insurance.

Assignee

Yvan Martin (CB)

Reporter

Yvan Martin (CB)

Links

0

Fix versions

Priority

Configure