I am using the beta Hierarchies functionality in JPD Premium and having trouble with Public Views and Connection fields. This happens if my Connection field is a project specific field OR a Global field.
Two primary problems.
Problem 1: If I apply a Filter in the Connection field as described here it works beautifully within JPD; however, this filter does not seem to translate to a public view as all of the “children” show up (speaking in hierarchy terms, not graph terms for ease of explanation) in the public view. See screenshot of internal (first) vs external (second) as well as the filter selection.Problem 2: I want to only show specific types in my view. This is easy enough internally - I simply add add a filter type to control which ideas show in this view + group by the “parent” type. However, when a create a public view, the parent type is stripped out. This can be fixed by adding the parent type to the filter; however, I then end up with the parent items themselves which I do not want. If I filter out the group with no value (i.e. because types cannot connect with themselves stripping out No Value means I strip out all the parent objects) then I end up with no items at all in my public board. This happens when I group by a Connection field that's local to my discovery project or when I group by a Connection field that is global.
What changes need to be made to allow public board links to mirror internal boards when connection fields are involved? Thanks!
Hi @Jena Miller : we're currently reworking the filtering functionality for connections as part of the work to take it out of beta - I'm checking with the team about these issues and will get back to you tomorrow
I confirmed with the team: both will be fixed in the next few weeks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Excellent, thank you so much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.