Forge App custom field has disappeared from our production JSM screens

JSM Development JSM Cloud
, ,
1

Hello community,

We have developed three custom fields to use on our JSM instance, based on the Forge Risk Assessment example code. These are for Incident Priority, Problem Priority and Request Priority. Up until this week, they were working fine but now the fields have disappeared from the agent views on these issue types.

I wondered if this might be related to the Forge developer now being “live”?

I have reached out to Premium Cloud Support but they don’t have a support channel for Forge Apps as of now so wondered if anyone else has experienced this?

I have upgraded the Forge CLI on our app and re-deployed/re-installed in into our production cloud instance but still no luck.

Any suggestions out there?

Thanks!

2

Hi @AndyHockenhull,

In order to help, I will need to understand the problem in more detail.

What do you mean by “disappeared”? Are you using custom rendering? Are the fields still accessible via other means, e.g. REST API or JQL? Could you share some screenshots to make it clear which views we are talking about exactly?

3

Hello, thanks for this.

The fields are available when viewed in jsm queues etc, just not on the agent view. I have added some screen shots to show what I mean.
Screens.docx (886.7 KB)

4

screens2.docx (204.0 KB)
Hello, thanks for this.

The fields are available when viewed in jsm queues etc, just not on the agent view. I have added some screen shots to show what I mean.
Screens.docx (886.7 KB)

5

Also, I have just compared our code to the example risk assessment field code and noticed that the manifest.yml file structure for the jira custom field module has changed - I will try modifying our version and re-deply to see if that helps.

6

OK so success!!! if we modify the manfest.yml file to remove the data elements as we your commit on the Risk assessment field example, it now works as expected and is visible.

This is the code I removed.

data:
-        storage:
-          issueProperty:
-            key: forgeRiskFieldValue
-      readOnly: false
1 Like
7

I’m happy it’s working for you again!

We announced the data property deprecation in March: https://developer.atlassian.com/platform/forge/changelog/#15-mar-2021.

8

Morning community - it appears that the issue described above has resurfaced for our Forge apps. On the issue view/edit screen the Forge field does not render correctly. It is there when you view issues in queues etc and also I can see the field has a value when I use the rest api to render the fields but it is not visible to the end user.

As I test I have created a clone of the Forge Risk Assessment app and deployed it again to my dev jsm site but still no luck. This seems to have happened in the past two days or so.

I have checked the change log and cannot see anything that might refer to this.

Any suggestions please?

9

Hello folks - I found the issue - it was the ui kit that was updated in the change log on the 19th Oct. - Note to self - read the change log going forwards!!