Udf's need to populate across entities

[Tuboysdad]

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.

[kimblerc]

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

[Spiegel]

Thank you for raising this need.

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

Regards,

Ofer

[kimblerc]

@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

[Spiegel]

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.