Gezim Shehu [Communardo] Community Champion

@Scott Theushahaha this is way too cool. Unique approach. Thanks for sharing

This might be similar. We have 2 blocking sub-task issue types. If one resolves, checks for the other, if also that is resolved, it transitions the parent. Let me know if you need any help adapting it. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import…

Hi, This is a great question. We also have experienced something like this during our first upgrade. There are some best practices tips here https://confluence.atlassian.com/ug/best-practices-guide-for-upgrading-jira-software-server-933696757.html However due to high level of customization, we had to come up with our own…

Do you have any possible scripting add-on? I can gladly help with building the script. If no, maybe someone else can relate to your current setup.

Are you referring to this for the client? https://almworks.com/jiraclient/overview.html Being offline I don't see how they can communicate in the first place.

I'm not so familiar with BobSwift, however the link relation between two subtasks does not exits. In theory they are not linked at all with each other. Parent/Subtask relation exists only 1to1 (parent to/from subtask)

Hi, You would need an automation, or even better a scripting add-on. From there, sure you can and also much more. Br

Never experienced this, but imo could be something with the browser/config.

@Michael Johnsonhi, Is this still available? Best Regards

Are you testing on the same workstation/pc?

How do you want to filter it? By attribute (Object Name)?

You could either use any add-on (emailthisissue for example) and send an email to a group, where in your case group could be licensed users (or every group which has access). Or even better, just use the banner instead as suggested above.

I cleared JIRA internal caches (using Script Runner built in function). Also tried approving with different users. Same results. On the same approval step.

It's a bit unclear what you're trying to achieve, but in case you are talking about the overall project status, well there is no such thing directly implemented. However a quick workaround is possible: * Create an issue type called "Project Status" * Project Manager can update that issue to represent the overall project…

Hi, Depends on what "assets" / plugins you got on your disposal. I don't think running a JQL query or even a REST call to retrieve and interpret the mentioned results, is doable right out of the box.

Great article :)

I am able to reproduce this on a 4 approvals workflow). At the 4th, the error always occurres.

How are you trying to send the custom field? You should do it by id (id of field in the other instance)

Did you find where the error was?

My vote also goes for a scripting add-on. You do not need to purchase one, but highly suggested. Simple script would do.

Why not just restrict access to that Service Desk project?

It's definitely a must if you want to get into deeper level of customization/automation.

Since you mentioned Service Desk Portal, I figured this was needed. It's "Extension for Service Desk for JIRA". In your case, within JIRA Software, I would suggest to use scripted fields (you would need ScriptRunner installed) and the field context for the desired project could display on the fly info/text , in your case…

Hi, By 'robot', I mean a custom (JIRAinternal) user created for automation purposes. For SD , it needs to have Agent permissions/license to run rules. Br

Np. Glad to help

I though SLA data during weekends was the problem :), hence the suggestion. I'm not aware of any feature to filter dates in Service Desk reports, but maybe you could get creative in the JQL. Still long shot.

Go to Service Desk Project->Project Settings->SLA and check which is the defined calendar. You can define working days/hours there.

Most likely, you would use the "robot" user here. (and everywhere else where automation occurs) Setting the default user, which rules run on can be done here: Service Desk Project->Project Settings->Automation

Hi @Stian Bentsen Sveen, I remember also having troubles with getting the Service Desk request names. By default, using only normal methods to retrieve the value from Customer Request Type custom field, you would get the key, instead of the name. Key looks something like this: "rsd/2aed6e92-1695-4928-9926-8475e36d40ad"…

@Mark Markovalso has a good point. Behaviors would be my choice also, since in your case you have already defined a default value for the field. Though issue is that you would monitor 2 custom field for changes. Also it would require 2 updates, that's why I suggest you remove even the default one and add a post function at…