Known issues
Looking for the documentation on the newest versions of Power Scripts for Jira 8 for Server/Data Center? Click here !
We all strive for perfection. We do realize there is room for improvement, and we are working to resolve but haven't resolved the following issues just yet.
Here you can see a list of common problems, explanations, and their resolutions. We will update the page with each finding.
| Affected functionality | Problem | Explanations and resolution | |
|---|---|---|---|
| 1 | editor, templates | Template checking still checks for SIL™ syntax, instead of the new Template syntax. | Reason: not implemented yet, is in our roadmap. |
| 2 | runner gadget | The runner gadget is not rendered after the 4.0.0 upgrade. | We changed and renamed the key of the gadget. All the scripts have been migrated to the new one. All you need to do is to remove the old gadget and add a new one to your dashboard. We migrated the scripts in your new gadget, so after you re-add the gadget to your dashboard you should be able to see them configured. |
| 3 | database configuration | Certain configuration from the database disappears (for example, some of the SQLs from the Database Custom Fields page) | Because Oracle treats an empty string the same as a null value, and due to a bug in our upgrade task, it may happen that you lose some configuration from your database. Resolution: Oracle upgrade guide. |
| 4 | Issue history | When the addWorklogAdjustEstimate() worklog routine is used, duplicated TimeSpent entries are made in issue history. | Duplicated TimeSpent entries result in incorrect calculations in the Jira report functions which use the history. We are working on a workaround. |
| 5 | JQL functions | Receiving error: No signature of method:com.keplerrominfo.jira.plugins.jjupin.jql.jiranative.SubtasksOfJQLFunction.getQuery() is applicable for argument types: (com.atlassian.jira.jql.query.QueryCreationContextImpl, com.atlassian.query.operand.FunctionOperand, com.atlassian.query.clause.TerminalClauseImpl) values: [com.atlassian.jira.jql.query.QueryCreationContextImpl@13fc1fdb, ...] Possible solutions: every() | Jira does not impose rules on the JQL functions which can cause conflicts when two plugins are trying to define the same function. For example, if you are using Power Scripts for Jira subtasksOf JQL function, and another plugin has defined a JQL function with the same name, you need to disable the Subtasks Of module from the plugin where you do not use that JQL function. |