Gezim Shehu [Communardo] Community Champion

Many thanks for sharing!

Nice to meet you @Nich Hogue . Great to have you in the community!

Hi, I guess you could use 2 fast-track transition post functions on the current transition. I'm mentioning this, since you have tagged this with scriptrunner. So let's say you start from Status A. You have a transition from Status A to a Temporary Status. This transition contains 2 fast-track transition post-functions,…

Hi, Sorry for the confusion, I had replied about an app who can do this. Even though the app is a scripting one, I mentioned that there was a built-in feature (of the app), which requires no scripting to create a linked issue. Then I also linked the manual way, which is the built-in feature of JSD itself. Cheers

It's not in the automate section. Check this link out, it has the details. https://confluence.atlassian.com/servicedeskcloud/blog/2016/02/create-linked-issue

Hi, You could set it as a hidden field in that customer request type, with a predefined value. That however would mean the field would be shown only after creation of the ticket (if it's the portal I don't see this as a problem). Else, you would need an app from the marketplace (or build your own :P). This might be helpful…

Hi there, Typically a release would be used only "once". Meaning stuff that is released is considered Live/Production. I would not personally suggest to use releases how you describe them. You could surely introduce a new metric for keeping track of the stages where your code is though. Either simply a status in the…

Hey @[deleted] , Welcome to the community. Regarding the question, well it depends on how deep you want to go. It can be simply business projects to keep track and visualize your EA Team's work, or either map the infrastructure and services with something like Insight - Asset Management for Jira. You could visualize all…

Can you test and just run it once? Also check if you have all the imports.

You have quite a lot going on in your script. However, here's a quick and short script to set a user custom field of a linked issue = assignee of original issue. I also implemented your required conditions/checks. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import…

Here's a thread which describes what you need https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-to-create-customer-groups/qaq-p/24570

Swap out - I mean change. So if it happens that your requirements for one of the 50 projects change and you need different permissions, you could easily just change the project role membership. And you are saying to create a group and put that group within the service desk team project role? Yes, that's what I suggest. It…

Yes, no one will be able to see if they are not licensed. Only portal access.

I would surely suggest to use 1 shared permission scheme. It would make your life easier. And configure the permission scheme based on Project Roles. If needed, in the future, you could swap out membership of those roles for further customization. Then for now you could simply add a group with the users you like "My Team"…

That group in theory only gives them the JSD license. How is your project(s) configured. Could you share how many projects you plan to involve, permission scheme and project roles current config. So I could provide a proper suggestions.

I'm assuming the IT staff, each of them has a JSD license? Or do you use JSD in conjuction with Jira Core or Software? If they need to interact with the tickets, portal would not be a good idea. That's mainly for the customer to get updates, comment and occasionally trigger a transition. Yes, ira-servicedesk-users is a…

Hi, I would suggest a group, if it's the same repeated set of people. If different people, but with the same function, then put them in project roles. What do you mean by adding customers? Organizations are mainly intended for portal use, so yes customers only. Cheers

Ok, it's more clear now. In Jira, you could do these either based on Project Roles Groups People (reporter, assignee, etc) ,etc But teams and organizations not. Team is not a unit in Jira. And Organization is only applicable to Service Desk. You could easily use groups for this though. Also there are apps out there who…

I don't really understand your question. Could you provide further details?

Sure. Glad to help.

Not really detailed sorry. I don't think anyone will understand this :)

Could you check the workflow? Specifically the create transition?

Just a thought, maybe you could use Groups? If yes, then a Group Select Field custom field would do the trick. You just need to set it accordingly (project a or b users). There's also the possibility to synchronize groups and organizations, but you would need an app for that.

Sure anytime, Cheers

I think this is normal greyed out. Maybe you want to set it hidden then?

Forgot to put in the boolean argument. What do you mean yellow? Does not happen to me

Sure, you could either add a mapping for the custom field, or simply append this line after setting the custom field value getFieldByName("User Priority").setReadOnly(true)

No that tutorial involves javascript, meaning using Jira stock. You just need to create a scripted field, select it's output format (template) "HTML". Then you can use groovy to calculate the logic and return a html in string format. Example def returnArg switch(issue.priority.name){ case "Low": returnArg = "green" break…

If you create a Scripted Field, it does not hold any value. It only renders what you have scripted, on the fly. So if cf2 is outputting a value, based on cf1 value, then if cf1 changes, also the cf2 output will change.

Try and change the mapping type from Service Desk, to project/issuetype