Gezim Shehu [Communardo] Community Champion

Hi, Really depends on what you use JIRA for. If standard SDLC (Software Development Lifecycle) I think the already built ins are enough.

Im not sure. I'll try and check again at the upgraded instance I have access

Hi, I would go with including a post function to set the organization to (All Customers - assuming that's the name of the org which includes all users) in that workflow (only for that issue type if many) Br

Hi, I also get errors. These however are script runners type error/warning. In my instance it executes fine. Have you tested in a workflow? Br

Hi, I'm interested. Can I have an email contact? Thanks, Best Regards

I did not make changes to that. It worked just by the one line fix :)

@Hugo NoronhaI tried and you are right it didn't work. However debugging quickly i found that the output of organization.toString() now has changed so i replaced it instead with organization.name Now it works

Im on JIRA 7.3.0 and SD 3.3.0. But I have a dev instance currently upgrading. Let me check there later

Sorry, misunderstood. Have you tried using organizations? https://confluence.atlassian.com/servicedeskcloud/blog/2016/09/group-customers-in-organizations

Did you try running the script in a post function ? I pulled it out of a functional workflow. Should be ok, despite the warnings. Just put it in the last order

I'm not completely sure if you mean projects or issues. (projects created by: always JIRA admin and not users) If projects * Use 1 permission scheme, defining browse project permission to a project role "Users or Viewers" * Assign group or users to that project role for each project (project role is suggested instead of…

@Hugo Noronhayou have mistakely inserted your dev url I think at the end of the post "Cancel"

Below is a script I use to add an organization on create issue/ticket import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.ModifiedValue import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.issue.util.DefaultIssueChangeHolder import…

I've encountered this issue a couple of times, but it was an issue with user sync. AD synced groups are configured for application access in our case. Resyncing (removing user and adding into a licensed group again) fixed this. Try if you can add the user (reporter) as a watcher in Service Desk project view for the issue.…

Hi, Are the required fields included in the form?

Below is a script I use to get attribute value from Insight Object. Specifically JIRA User type. I get the username out of it and then build a comment mentioning those users. But in your case you could adjust it to add the usernames to a (multi) user picker. import com.atlassian.jira.component.ComponentAccessor import…

Hi, Great question. Best practices about abstracting JIRA "parameters/attributes" are always good discussions. In my opinion, Issue Type should be really used to answer the question "What is it?". In your case a refund. You have to keep in mind the way the issue type really works, so configuration wise. 1 workflow x 1…

This sounds like serious issue, which I'm afraid I cannot help. How about opening a support ticket, along with support logs generated? That might start to clarify the issue. Maybe it's even infrastructure wise.

If you have only a few licensed groups, how about removing application access?

This is very broad and I'm not sure how we can help you with no details. Can you provide some? For example any recent changes in infrastructure or configuration? Any addons used that impact the Service Desk project and/or portal? Cheers

This is a script I use to transition linked issues. I assume you can just adjust to use it as a condition import com.atlassian.jira.user.* import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.link.IssueLink import com.atlassian.jira.issue.* import…

I usually use the "old" method to transition, by calling the workflowTransitionUtil WorkflowTransitionUtil workflowTransitionUtil = (WorkflowTransitionUtil) JiraUtils.loadComponent(WorkflowTransitionUtilImpl.class); workflowTransitionUtil.setIssue(mutableParentIssue); workflowTransitionUtil.setUserkey('userkey');…

I'm running Confluence on Server and have the possibility to allow unlicensed access. Which version are you running?

Hi @Michael Johnson, Can I contact via emai ? Br

Sorry for the late reply. in case you get all done issues you most propably forgot to set the post function. go to the specific workflow, to the Done transition. check the post functions. If none is specified for update resolution field add a new one

Agents users who can actually "interact" within the Service Desk project with it's specific functionalities. If you have also JIRA Software, you could get some usage as it's still accessible by JIRA Software users, but very basically (view, comment INTERNALLY only - meaning that these comments will not be available to…

Hi Nora, I'm not fully understanding the question. However, ofc you can use specific Service Desk queues to sort requests. But for agents not customers. Customers can have different portals, requests types (divided in groups, maybe this helps you) and the Help Center overview. When you talk about the help center are you…

Sorry don't have much time to refine this. But the basics are here. Just add a new Script Listener, for your desired project or ALL (you can also define conditions in the script for example if(issuetype = task) etc) Run the listener on event Issue Updated Inline Script import com.atlassian.jira.component.ComponentAccessor…

Hi, I'm assuming that you are listening for epic creation and creating issues linked to it? In that case after creation, ofc the fields are editable. That is if the workflow status and permission allow. Maybe I'm missing something in your question. Cheers

Do you have groups for teams? Maybe you could use memberOf within the FROM. If urgent just use SQL towards the DB