Comments
-
Hello, I'm afraid this is not possible without an external app. There is automation rules for service desk but they don't include custom field changes. But if you have, you can use Script Runner plugin's Escalation Service feature for this. Regards, Elifcan
-
Hey @Jorden Van Bogaert Thank you very much for the detailed explanation. These are my assumptions too, but I wanted to get confirmation. Best, Elifcan
-
Hi, This is the official documentation for script field: https://scriptrunner.adaptavist.com/5.0.4/jira/scripted-fields.html A custom script like below would do: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.user.ApplicationUser import…
-
Hello, What do you mean "grammatically"? But since it's a cloud instance, you don't have access to Jira logs, anyways. Regards, Elifcan
-
Hello, Jira doesn't allow comparing two date fields at the moment, I'm afraid. You can use Script Runner plugin's date compare feature for this: https://scriptrunner.adaptavist.com/4.3.1/jira/jql-functions.html#_datecompare Regards, Elifcan
-
Hello, If what you need is simply to find the number of tickets created in a time period, you don't need the logs. You can just use JQL search and search for the issues. For example: created >= "2018/05/01" AND created <= "2018/05/02" This will show you how many issues created in that time period. Regards, Elifcan
-
Hello, Yes, you can achieve this by using Automation feature of Service Desk. In fact there is a rule that you can use for this purpose called "Comment re-opens Issue" You can find Automation on your project's settings page. Regards, Elifcan
-
Hello, Here is what you can do, but you need two add-ons for this: Jira Suite Utilities and Script Runner. First with JSU plugin, you can add a regular expression validator on your create transition to make sure user enter a number between 0-199. Second, you can create a scripted field with Script Runner plugin and add %…
-
Hello, You didn't write where you are using it, I assumed service desk template comments. First of all when you return something, script stops working at that point. So because you return true on the 4. line, this will not work. Second, you should be using it like this: import com.atlassian.jira.component.ComponentAccessor…
-
Hello, As I stated earlier, you can not restrict System Administrators from doing anything. Also assignee and reporter cannot see who has access to the issue, you are correct. But there is not a technical solution for your problem. You need to make only people who are reliable as System Administrators for your instance and…
-
Hello, Your question is not very clear. Can you give details about what you really need? Regards, Elifcan
-
Hello, Have you tried specifically deleting cookies related to id.atlassian.com? Check out this documentation: https://confluence.atlassian.com/cloudkb/oops-you-ve-made-a-malformed-request-when-resetting-atlassian-account-password-900816987.html I also found another question related to this, they stated it was because of a…
-
Hello, This is probably your Jira's base url is wrong. You need to change it to the url you are using: Regards, Elifcan
-
I found a bug report which seems related to your issue? Can you check this out? https://jira.atlassian.com/browse/JRASERVER-42609 What Jira version are you using? This may be your problem. Because I couldn't think of any other reason but a bug at this point.
-
This script seems like missing some important parts. Did you copy the whole script? Because there should be an else like this: else { issueService.create(user, createValidationResult) } Also which user do you use as "user", the logged in user or a static single user or anybody else?
-
Is there a default assignee on the project itself? You can check it on project's settings > Users and Roles. Could there be default assignees based on components? You can check it on project's settings > Components. Could there be a property on the workflow statuses such as jira.permissions.assign.denied ? This error…
-
Hello, You can add it to the postfunction of your workflow if it will be only updated via transition. Or you can add it as script listener that listens to issue updated event and updates whenever one of these two customfield changes. Regards, Elifcan
-
When do you set the issue security level? While creating the issue? If it's the case I guess you can write a customized script that runs on issue updated event, that checks change history and if security level field is changed, you can get the old value and update it with it. But I'm not hundred percent sure this would…
-
Hello, Yes you need to use branch variable stated in the documentation. What you are using is repository name variable. https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html Check out bamboo.planRepository.<position>.branchName variable. Regards, Elifcan
-
Hello, Something like this should work: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.user.ApplicationUser import com.atlassian.jira.issue.fields.CustomField import com.atlassian.jira.event.type.EventDispatchOption def issueManager =…
-
Well, unfortunately you can't restrict a system admin from making any kind of changes on Jira. Even if you create project level permissions and make certain people project admin, a system admin can always change the security schemes, project membership and permissions. For your second question, if you set security levels…
-
Hello, This is because you cannot add a new transition to a status where there is no going transition from that status on a used workflow. You need to first make this workflow inactive. So what you need to do is copy the workflow you are using, make your changes and then use this workflow on your project. Regards, Elifcan
-
Hello, This is not much information to go on with. I suggest you check System errors page first. You can access this page by going to Bamboo administration > System > System Errors. If there is no related errors, then I suggest you check Bamboo instance errors under the installation directory in the logs directory.…
-
Hello, Could it be because there is a screen on create transition of the new issue you are trying to create? There may be required fields on these screen like assignee. Or there may be a post function that sets the assignee on this create transition. I suggest you check the workflow of the new issue you are trying to…
-
Hello, It's not possible to give permission for some system admin features to some system administrators. If you don't want all administrators to have access to system admin features, you can use Jira Administrators global permission instead. Regards, Elifcan
-
Hello, You can write a customized script for this purpose. You need to do a jql search on this script where you search for issues that have the same summary. After that you can create a link for these issues. You need to put this script on the post function of create transition on your workflow. Regards, Elifcan
-
Hello, Check out rest api info page: https://docs.atlassian.com/software/jira/docs/api/REST/8.4.3/?_ga=2.246344448.522858717.1575535806-747249076.1541400997#api/2/user Is this what you are looking for? Regards, Elifcan
-
Hello, I see that you are using h2 database. I can't think of or find anything else to solve the issue :( Maybe you can try using an external database? Regards, Elifcan
-
Hello, These are all info logs. Are there any error logs in the log file? Also you can try to stop confluence, delete plugin cache directories and restart confluence again. These are the directories:…
-
Hello, It looks like something is wrong with web panel plugin. Did you apply the resolution stated here: https://confluence.atlassian.com/confkb/error-rendering-webpanel-no-renderer-found-for-resource-type-300814261.html Regards, Elifcan