Unable to create labels in suborg

[nllong]

Create a sub org and try to create a label using the UI.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[nllong]

Marking as p-1 to keep it from becoming stable.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[RDmitchell]

I will test on the latest dev solution

[RDmitchell]

Instance: dev1 SHA: f9558b8bb Org LBNL 101 SubOrg2 RM+20

It is possible to add labels to data in a sub org, but the labels are not showing up in the List View, at least for the Tax Lot tab Jurisdiction Tax lot ID: 10102/5B193 has a label, as seen in the detail view (added in List view) But in the list view, you can't display the labels

The same is true for the Property Tab List View This record has a label

But it doesn't appear in the List View

[RDmitchell]

The reason why the labels aren't showing up in the List View is because I didn't specify "Show in List", which is set in Org/Labels.

When I go to the Org/Labels view for the suborg (LBNL 101 SubOrg 2) I don't see any labels.

But in the Property List View for that Suborg, I am able to add labels "on the fly"

[RDmitchell]

When I try to create a label "on the fly" from the Property List, when I click the Done button, I get a 500 error

[anchapin]

I'm seeing the issue on my end also where you can't create a new label from the suborg, however, I did notice that when I assign a label to a suborg property that was set as "Show in List" in the parent org, then I can see it in the Inventory List.

The question I have then is whether we want users of the suborg to be able to create and edit labels? Additionally, would we want the labels and the label settings, such as "Show in List" toggle, to sync between the org and suborg or be unique? This type of situation will need to get vetted prior to or during the upcoming account hierarchy tasks.

[nllong]

@anchapin that is exactly the right question. I suggest we add this discussion to the accountability hierarchy discussion, that is, where do labels live within a hierarchy? How does that impact hierarchical aggregations? Adding in @haneslinger too.

[haneslinger]

My assumption is that sub orgs were not designed to be allowed to create/delete/edit labels, however, the "on the fly" label creation was forgotten about. That's why it returns a 500: it was never suppose it work.

In my accountability hierarchy proposal, I dissolve suborgs as we know them completely, as their implementation is not robust enough carry the requested functionality. In the proposal, orgs contain groups, and each group either has a parent ( like a sub org) or is the singular "root group" for that org.

As in the current implementation, not root groups should not be able to create/edit/delete labels. We should be mindful not to forget the "on the fly" ui while we implement.

My point is: This will all have to be refactored anyway, so let's close the ticket

[RDmitchell]

@haneslinger -- I think your proposal makes sense. I don't think anyone is using sub-orgs, and as you say, we will be completely refactoring that functionality for the accountability heirarchy.

So I do think it makes sense to close this issue. I will do that.