Jira/JSM DC Asset Object Configuration won't save

[Trudy Claspill]

Using Jira 9.12/JSM 5.12 Data Center

I have set up an Asset Schema with Objects.

In Object Configuration for one of the Objects I have added an Attribute of type User.

I want to specify User Groups for the attribute to restrict which users can be selected. 

I add a number of groups and click the Update button next to the attribute. I see the button "click" on the screen but otherwise there is no change to the screen. The attribute configuration remains in edit mode and no message is displayed anywhere on the screen. 

If I reduce the number of groups I've specified, then the change is saved when I click Update.

The limitation does not appear related to the number of groups specified. In my first attempt I could not add more than 10 groups. In another User attribute I selected different user groups (with longer names) and couldn't add more than 6 groups.

Has anybody else encountered this?

[Trudy Claspill · Accepted solution]

I have opened a support case with Atlassian. I will report back here what I learn.

[Trudy Claspill]

Closing the loop on this, here is the response I got from Atlassian Support.

It is failing because of the char limit of column TYPE_VALUE on AO_8542F1_IFJ_OBJ_TYPE_ATTR table

I was able to recreate the problem on my test environment running Jira 10.3.5 and I can confirm this background failure is not thrown on the UI, which is very misleading, as the users won't understand that it failed to include the group on the attribute.

I am going to open a new bug for this and will share the link with you.

As a workaround for the background error uou could adjust the char limit of VALUE_TYPE. Postgres example:

alter table "AO_8542F1_IFJ_OBJ_TYPE_ATTR" alter column "TYPE_VALUE" type varchar (400); 

I opened the new bug: Adding a few groups (or with too many characters on the group name) on User type Attribute of an Object fails silently

And also a feature request: Increase varchar for TYPE_VALUE column on AO_8542F1_IFJ_OBJ_TYPE_ATTR table

[Marc - Devoteam]

Hi @Trudy Claspill 

This could be a bug, as related to what you describe, the field seems to have a character limitation.

I can't reproduce it as I don't have som many groups and not with long user names.

Might be worth to raise this with Atlassian Support.