Error Creating Subtask In Jira Permission Exception
issue does not exist or you don't have permission to view it.Log In ExportXMLWordPrintableDetails Type: Bug Status: Closed Priority: Medium Resolution: Fixed Affects Version/s: 2.7.5 Fix Version/s: 2.10.0 Component/s: JIRA Integration Labels: bug-bucket Description Premises: FishEye 2.7.5 JIRA 4.3.4 JIRA FishEye Plugin 3.1.5 Summary: When trying to create a sub-task in JIRA from a Crucible review, this error is displayed in a popup: Error creating subtask in JIRA: com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it. What have been tried: Granted all possible project permissions in JIRA side for the user that's logged in both sides; Enabled all three authentication methods in the App Links configuration to see if it makes any difference (tried with only Trusted Applications first); Checked that the JIRA issue linked in the Crucible review is opened; Still get this error. I'm attaching FishEye logs with extra debugging information for investigation, as well as atlassian-jira-security.log from JIRA side. atlassian-jira.log didn't log anything. AttachmentsOptionsSort By NameSort By DateAscendingDescendingThumbnailsListAttachmentsatlassian-jira-security.log0.7 kB01/Feb/2012 2:44 PMfisheye-debug-2012-02-01.log30 kB01/Feb/2012 2:44 PMfisheye-error-2012-02-01.log17 kB01/Feb/2012 2:44 PMIssue Links mentioned in Wiki Page Loading... Activity People Assignee: Unassigned Reporter: Felipe Kraemer Participants: Felipe Kraemer, Nick Pellow [Atlassian], Peter Grypdonck, Trey Hyde Votes: 12 Vote for this issue Watchers: 6 Start watching this issue Dates Created: 01/Feb/2012 2:44 PM Updated: 04/Feb/2013 3:16 AM Resolved: 04/Feb/2013 3:16 AM Last commented: 3 years, 36 weeks, 1 day ago Atlassian JIRA Project Management Software (v7.2.0#72002-sha1:36e1562:node2) About JIRA Report a problem Atlassian
misconfiguration Exception message is misleadingLog In ExportXMLWordPrintableDetails Type: Bug Status: Verified (View Workflow) Priority: Low Resolution: Unresolved Affects Version/s: 4.4.5, 5.0.7, 5.1.8, 5.2.11 Fix Version/s: None Component/s: Project Administration - https://jira.atlassian.com/browse/CRUC-6038 Permissions Labels: None Symptom Severity: Minor Support reference count: 17 Description Incorrect Exception message thrown, which misleads users. Also see https://jira.atlassian.com/browse/GHS-3325 The Exception thrown when entering a permission https://jira.atlassian.com/browse/JRA-26375 related workflow step variable looks like following: java.lang.RuntimeException: Error parsing meta attribute false. Name format is 'jira.permission.[subtasks].
sub-task post-function produces error on setting Security Level10-1Ed Letifov (TechTime, New Zealand)Sep 30, 2014I am migrating a JIRA/JIRA Service Desk project setup from a test environment to production https://answers.atlassian.com/questions/9380754/scriptrunner-create-sub-task-post-function-produces-error-on-setting-security-level at one of the customers. The version of JIRA is 6.3.3, https://answers.atlassian.com/questions/13406338/random-errors-with-clone-issue-post-function version of ScriptRunner originally was 3.0.3 now 3.0.5.On create transition we have several create sub-task post-functions - in production every one fails with the following exception, while it continues to work perfectly in test. Migration was performed with Project Configurator + manual tasks afterwards. Does the below a error creating symptom of db corruption or pure failure in ScriptRunner code? Any ideas how to recover/insert the missing property? For everybody's amusement the mystery of this real-life clusterf$#k revealed:1. "The anvil": In my workflow on create transition, there are several ScriptRunner post-functions creating subtasks. Each has a condition based on the issue type being created. Out of these - 3 error creating subtask create subtask AND assign a security level other than the default one.2. "The hammer": What really was throwing all this off: my test cases specifically were using issue types that either a) shouldn't invoke any of the subtask creating post-functions b) should invoke one, other than the 3 mentioned above3. "The grain of sand in the big machine": These 3 post-functions had a line writing to log i.e. "foo" and "securityLevel" are the names of variables several lines above i.e. 4. "Don't fix what ain't broken": In the test environment (working), this particular string in the debug statement had a typo - the reference to "foo" variable had a wrong opening brace e.g. "$(foo}" and also "securityLevel" one was missing curly brackets and a space in front e.g. "... to$securityLevel". 5. "Repeatable, hence fixable?": Every time when we transferred to prod, being perfectionists, these typos were fixed ("The environments are exactly the same!" he said... yeah, right)6. "The result": a reference to a local script variable, inside a string, in a debug log statement, under sever
clone issue post function210greg brailsfordMar 10, 2015We use script post function clone issue with links. The problem does not seem to be with the data or the current user of the transition. We have tested it were the same issue and same user will reuse the transition and the cloned issue will work properly. I would put the failure rate at about 10%. It has not been a serious problem until recently because users are creating issues but they don't have visibility/permissions to confirm if they have been made correctly. I assume it has something with to many requests in on database at the same time. However that is hard to confirm. Here are some details of what we have in the post function settings:We don't have any conditions and the additional issue actions arecheckLink = {link -> false};checkAttachment = {attachment -> false};issue.summary = 'Implementation | ' + issue.summary This is the error we received: 2015-03-04 08:09:50,419 http-bio-8080-exec-11 ERROR chad.casey 489x5675x1 3nqz1q 209.33.217.188,199.21.206.132 /secure/CommentAssignIssue.jspa [scriptrunner.jira.workflow.ScriptWorkflowFunction] Script function failed on issue: IM-627, actionId: 11, file: nullcom.atlassian.jira.exception.CreateException: Can't transition workflow instance #195121. Current state is 0, requested state is 1 at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:722) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:622) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssueObject(DefaultIssueManager.java:735) at com.atlassian.jira.issue.IssueManager$createIssueObject$1.call(Unknown Source) at com.onresolve.scriptrunner.canned.jira.utils.AbstractCloneIssue.doScript(AbstractCloneIssue.groovy:96) at com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.CreateSubTask.super$2$doScript(CreateSubTask.groovy) at com.onresolve.scriptrunner.canned.jira.w