Display conditions are now available for some Jira modules. Using display conditions, you can control the visibility of your app modules in the UI. See the modules reference documentation to know which modules you can use display conditions for.
Run npm install -g @forge/cli@latest on the command line to install the latest CLI version with linting for display conditions.
BUG FIX for custom UI resolver types
The return type of custom UI resolvers now accurately reflects that you can return a string. This change prevents inaccurate type errors from showing up when using TypeScript with custom UI.
BUG FIX for the UI kit useEffect hook
We’ve fixed a bug where the useEffect hook would be called more than once when called with an empty dependency array.
Run npm install -g @forge/cli@latest on the command line to install the latest CLI version.
This is exciting news! However I was surprised to not see display conditions based on a custom issue property. This would be a much more powerful mechanism and would allow a developer to toggle their issue panel based on whether custom data is present or no. Atlassian Connect has this feature and it’s quite popular.
1: This helped. it is issueType: Sub-Task – dashed case AND case-sensitive: The capital T is important. Maybe we could add the possible array value to the docs.
2: Thank you for the clarification. Do you have an idea how to check whether the project supports “sub-task” issue type using conditions? I think it is not possible with the current conditions.
@JulianWolf I’m glad to hear it worked! We will be working on improving the feature and its docs in the future and your feedback will be taken into account!
About option 2 - it is not possible to do it at the moment using display conditions. You may display a message inside the app that the project doesn’t support sub-tasks after checking it using public REST API.
After run npm install -g @forge/cli@latest, I updated to forge version: 1.0.0. Then forge deploy, I get error: Error: EACCES: permission denied, open ‘/Users/art/Library/Preferences/@forge/cli-nodejs/config.json.1237953050’