Konrad Kleine

> This will prevent creating spaces with a name that cannot be used > as a value in pod labels. @xcoulon I find it highly interesting in the first place...

> @kwk right, the space name rule is bound to the namespace rule, indeed. That's for now the simplest way to create resources in relation with a given space on...

> It looks like the type of value for the field business_value in ctx.payload is float64 instead of int @jarifibrahim what happens when you update the business value with a...

Please note that any member name (also the one of a relationship) must follow these rules in JSONAPI http://jsonapi.org/format/#document-member-names. One of the key takeaways is that the dot-character is a...

@jarifibrahim essentially any field that has a "complicated" type (e.g. lists and markdown fields) is currently handled by name and not by type. So all the special behavior is solely...

@DhritiShikhar technically this cannot only happend for state but for all kinds of fields that have the enum type. Are you planning to take that into consideration?

> @kwk yes but this is hardcoded https://github.com/fabric8-services/fabric8-wit/pull/1973/files#diff-175cd1756eb938ba265113030ff9eedfR54 So it is not respecting the WIT itself.

@aslakknutsen well, hm. That is bad. Before I've implemented this PR #1943 I saw that we were delivering the `system.number` field in every planner-item-based work item. In other words **every...

@aslakknutsen I think I was missing this change: ```diff diff --git a/workitem/workitem_repository.go b/workitem/workitem_repository.go index 859dfc5a..92fbaa42 100644 --- a/workitem/workitem_repository.go +++ b/workitem/workitem_repository.go @@ -494,7 +494,7 @@ func (r *GormWorkItemRepository) Reorder(ctx context.Context, spaceID...

@aslakknutsen > @kwk related? Haha, yes. It demonstrates that the dynamic form is actually working with the old system.