Comments
-
Do I understand correctly that you want Customers (these users can only login to portal) to create tickets in a Jira software project from email?
-
Hello, You need to create a email channel for portal users (customers). You can read more information here https://confluence.atlassian.com/servicedeskcloud/receiving-requests-by-email-747602718.html
-
Hello, If by access you mean the ability to view issue details then you have to add security schemes to restrict user access. You would create several security schemes and set them automatically on issue creation by a post-function depending on the issue type. You can read more about security schemes here:…
-
Hello, You can not search on the JSON result. You would need to write your own program.
-
The last line should be labelManager.addLabel(myUser, $issue.getId(), String.valueOf(CalendarWeek), false);
-
What do you mean by updating issue history tab? You want to change the history of an issue? It is not possible
-
Hello, you can not do it out of the box. You would need an add-on for it. What is your Jira version (Cloud or Server)? Do you have add-ons like Power Scripts or Scriptrunner?
-
Hello, What are the errors?
-
Hello, You need to create a REST end point and then call the rest end from your web item.
-
Sorry for my mistake. If you want the transition button to be hidden , you should set passesCondition variable to false. passesCondition = false And your script should be like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.IssueManager import…
-
It means that event.getIssue(); returns null. Could you check it? Is it null? On what event your listener fires?
-
Try to enable outgoing logs and have a look in the logs
-
issue variable does not exist in your code. Do not use it in your code. You used it in serveral places. You defined only immutableIssue and you should use it. That is why it should be def config = cf.getRelevantConfig(immutableIssue) Fix all your code. The error means that you pass null to the getRelevantConfig method.
-
Hello, It is not possible out of the box.
-
The transition button will be hidden only if your script returns false. Try to put log.error in your code before all return statements and see if your script returns false.
-
Aslo you can troubleshoot your problems with the following article https://confluence.atlassian.com/jirakb/mail-and-mail-handlers-troubleshooting-211649643.html
-
If you accomplished the requirement then it is fine.
-
Condition must return true or false. Your script does not return anything. Try like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.IssueManager def issueManager = ComponentAccessor.getIssueManager() Collection subTasks =…
-
Hello, Validator do not hide transition buttons. They just check the input in the transition screen and can throw an error if the values are wrong. What you are looking for are conditions not validators
-
By the way try to reindex the project where the issue was updated and have a look if the value appeared.
-
Are there any errors on the listener? Are you sure that issueManager.updateIssue was executed? After issueManager.updateIssue try to reindex the issue. The code would be like this boolean wasIndexing = ImportUtils.isIndexIssues();ImportUtils.setIndexIssues(true);log.warn("Reindex issue ${issue.key}…
-
Hello, Accrording to your scheme current assignee will not get a notification when an issue was created. I mean if you create an issue and set an assignee for it then only support user wil be notified. Is it the case? Or even if you change the current assignee on an existing issue, the new assignee will not receive an…
-
Hello, You could update all existed issues with the critical information. Then everything would work as expected.
-
Hello, I would recommend you to submit a support request. Here is the link: https://jira.cprime.io/servicedesk/customer/portal/2
-
Hello, You would need an add-on for it. What Jira version do you have (Cloud or Server)?
-
Hello, setCustomFieldValue is not enough. You need to use the following method after it issueManager.updateIssue(userManager.getUser("user"), myIssue, EventDispatchOption.DO_NOT_DISPATCH, false) You can find an example here…
-
It is not possible for Cloud
-
You can find information when you should reindex your Jira instance here: https://confluence.atlassian.com/adminjiraserver073/re-indexing-after-major-configuration-changes-861253858.html But in your case it does not help.
-
No, these steps do not apply for the Cloud Server
-
Hello, It is no possible out of the box. You should use an add-on for it. There are a few add-ons available in the marketplace (Power Scripts, Adaptivist Scriptrunner). If you are on Jira Server/ Data Center you could use Power Scripts add-on. You could write your own JQL function which would cover all your requirement and…