Udf's need to populate across entities

Idea ID 1790229

Udf's need to populate across entities

We have an issue where we needed to create a "Teams" field for manual tests and then for manual test runs. However, since the  MT's and MR forms are for separate entities we need to create udf's for both Manual Tests and Manual Runs. However, that creates a problem where the data from that field needs to be entered on both  entities. We tried to create a rule that would allow us to populate data in one field based on data from another field in another entity (MT to MR), but cross entity rules don't exist. 

We need a way when a manual run is linked to single Manual test, that the manual run inherits the data from the field from manual test to provide a single source of truth.

4 Comments
Captain
Captain

Agreed, you should be able to share fields across different areas of the application. It's frustrating you cannot share fields.

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Accepted

Thank you for raising this need.

We have a feature for it on our backlog. However, no planned ETA for it yet.

Regards,

Ofer

Captain
Captain

@Spiegel I don't know if I should open a new thread for this.

 

Is there a way to have UDF's that have the same value across multiple entities?

Example- UDF Field "Teams" has a value of "MyTeam" in workspace X, but a blank value in workspace Y. We would like "MyTeam" to be populated from workspace X into workspace Y

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

This is indeed a whole new idea worthy of a new post.

However, it would probably be rejected at the moment.

The reason is, that though you can create shared UDFs that can be populated the same across workspaces, but the values of these UDF also must be common and shared across the workspaces (like lists, strings and integers, and Releases).

this is not the case for Teams, as teams is a workspace level entity. And even though 2 teams in 2 workspaces may be called the same, it is not truly the same entity.

So to support this idea Teams need to be defined at the sharedspace level. and for that there is no concrete plan at the moment.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.