Comments
-
Glad to help. Though I strongly suggest getting ScriptRunner, even if this case wasn't a must have requirement. You'll get so much out of it.
-
1- Use default Space Permissions and configure a user group to have view permission 2- Allow anonymous access (view permission only) in the desired Spaces and restrict only the private pages you want to kept hidden Each has it's own benefits and usecases
-
This is something similar. Change the custom field to component import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.CustomFieldManager import com.atlassian.jira.issue.fields.config.FieldConfig import…
-
Can you please check Customer Permissions in Service Desk Project? Customer permissions Who can raise requests? Customers who are added to the projectCustomers who have an account on this JIRA siteAnyone can email the service desk or raise a request in the portal Who can customers share requests with? Other customers in…
-
def cf = customFieldManager.getCustomFieldByName("Your Custom Field") def cfValue = cf.getValue(issue) if(cfValue == 'your desired value'){ issue.setAssignee('username') }
-
What do you mean by " This should work when there is a screen added during a Epic Transition to In progress." If you basically want to trigger Epic Transition on Story transition: -You need to include a script post function on Story workflow in the desired transition -Script needs to check for the epicParent, this is…
-
To transition correctly following lines are needed workflowTransitionUtil.setIssue(mutableIssue); workflowTransitionUtil.setUserkey('userToTransition'); workflowTransitionUtil.setAction(actionID); workflowTransitionUtil.validate(); workflowTransitionUtil.progress(); And generally speaking, your import lines should be less…
-
Yes issueFunction in expression("","assignee==reporter")
-
Do you have ScriptRunner or any similar script running addon? You could write a simple script, only for that link type preferably, and transition linked issue automatically. Service Desk by default offers some of this functionality, but very limited. Strongly suggest to get ScriptRunner.
-
Do you have Script Runner? I'm afraid as of built in JQL functionality, this is not possible.
-
Where are you running this script? Is it as a post function? If it is then it will only execute once the transition occurres. Maybe you could write a validation script, to only accept the value based on the first field's value?
-
You have to check Application Access. From what I understand you're using both Service Desk and JIRA Software. You only need to define JIRA Software Application Access to users (user groups) who really need it and remove everybody else. Then you can set the customer portal as open and configure sign up as public.
-
I don't know how Service Desk does this technically, but does exactly what you are asking. It includes search results from Confluence, and displays as a pop pup page (styled exactly like in Confluence). Maybe you could try and research how this is done.
-
How are your users configured? If you have them synced via AD, you have to remove the user from the (I assume) JIRA group you have configured to have application access. PS: Please fix the tag to JIRA not Confluence.
-
I think you need to specify the issue when getting a custom field value. Something like: customField.getValue(issue)
-
You must have some type of reference field, as the error message implies. If you have db access you could query the values (or the missing values) causing the error.
-
Could you post the whole script? I don't see any part where you check the subtask or parent relation?
-
No matter what I tried, IssueService.update worked only from script console. I added the below line and now it works if(updateValidationResult.isValid()){ IssueService.IssueResult updateResult = issueService.update(sdUser, updateValidationResult) issue.setOriginalEstimate(estimationLong) //added line log.info("Issue " +…
-
Are you able to find that user, let's say in a single user picker custom field?
-
Please mark my latest reply as the accepted answer, as that was the fixed one :)
-
Happy to help
-
Hi Alexey, That was my first approach (in fact I always put the script post functions last), though still the error persisted. Any ideas? Thanks
-
You need to get the config first. In your script you are trying to find an option directly from the custom field, which isn't valid. You must get the list of options available (aka config) first for that specific issue. Take a look and let me know how it goes:
-
Try defining the Default Security Level visible to Any User or something like a Project Role Viewer.
-
(Y)
-
Yes the last line is used to hold the value. There are several ways to do this, examples: Change Holder, IssueManager.UpdateIssue(), or either IssueService Class (which is what JIRA actually uses). Sorry my mistake that requires an option,as I was using that line by getting the value as: setCustomFieldValue(field,…
-
You don't need to import the 2nd line. issue.SetCustomFieldValue() just changes the value, but it doesn't hold it. To achieve this you could use the IssueManager class. It would be something like this: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.user.ApplicationUser //either get the…
-
Hi, Is the user you are trying to share with a customer on that portal? Best Regards
-
Hi, Yes, if you mean you accidentally open an issue and you want to delete that, you can. You would have to have the "Delete Issue Permission" configured in the Permission Schema used by that project. Though I'm not quite sure why you would have to do that often? Maybe you mean, mark the issue as somewhat not active? You…
-
Hi, The approach to this imo, is to run a check on issue create transition and check for a certain criteria, then set the appropriate issue security level based on it. This could either by done by using 2 separate issue types/workflows, or by incorporating into 1 workflow and base the criteria on some field value. Now both…