Derek Fields _RightStar_ Community Champion

Given how old your instance is, it may be easier to build what you want fresh in the Cloud and import your issues using a CSV import rather than going through the pain of upgrading several times to get to the minimum level to use JCMA. If you want to go through the upgrade route, you can create a Trial license for the data…

Glad you found it - I was about to respond with the same.

Quick update - the plugin that I mentioned is no longer free. It is a paid app. 

@Hendriawan - You can't have the Customer "send" the email because they would need a Jira license. But you can put any information from the Issue into the email itself using smart values. You can put the name of the Customer into the email itself by using the smart value {{reporter.displayName}}. For instance, you could…

I don't use Github, but I doubt that this is possible. Jira uses the Issue Key in the branch name to create the association between the Issue and the Branch. If you don't embed the Issue Key, there isn't any way for Jira to know how to maintain that association.

@Kroupova, Kristyna If you are able to log into Jira and access the filter, then the problem is on the Excel side. You need to make sure that you have set up Basic authorization with your username/password in Excel. Excel needs to pass your username/password as part of the filter request

@Kroupova, Kristyna - It looks like you have a login problem with Excel. If you look at the lines that Jira is returning, you will see <title>Sign in to your account</title> This indicates that Jira is returning a login page instead of the output of the filter.

I'm not sure that this is the best method. I would create a table with one column called "LOCK" as a primary (unique) key. Before I start to create the sub-task, I would try to insert a record into the table with a constant (e.g. "locked") so that if there is already a record, it would fail. If it succeeds, then create the…

The Version object has a getReleaseDate() method that returns the release date. It looks like you should be able to use VersionManager.getFixVersionsFor(issue) to get a collection of Fix Versions associated with the issue. Each of these can be queried using getReleaseDate() for the date. Does that help?

My article should have been explicit that this problem is related to internal inboxes, not the Atlassian provided inbox. If the Atlassian-provided inbox is losing attachments, you should contact Atlassian about this.

setFieldValue(null) is the correct call. I have done some testing on my environment and you are correct - it doesn't work. I would open a ticket with Adaptavist.

For JSM, the external users should be going to the JSM portal. This will aggregate all of their tickets into a single view.

1) You would need something ScriptRunner, with the inSprint() function or the previousSprint() function to filter to a specific sprint. 2) You can use fixed dates by specifying the fixed date instead of a relative date. For example "updated >= 2022-01-01 AND update <= 2022-03-31" will return all tickets updated in Q1 of…

Why not just put a "Company" field on the form and require it? 

@Ivan Lima That is awesome. Thanks for the direction towards the Role API. I wish I could find a matching Java API since I am writing my script in Groovy, but so be it. This will work for me. Thanks so much!

I appreciate the help. I have looked through the entire JSM Java API and can't find anything that appears to return customers who are not associated with an organization. I even looked through the database and can't figure out how they are associating customers with a project. It has to be in the database somewhere but I…

Take a look at Queues for Jira Service Management | Atlassian Marketplace - It runs on Cloud as well as DC.

@Demis Estabridis The problem of agents belonging to more than one team is real. Your two options are the only ones that I am aware of. For one of my clients with that kind of issue, we use Cross-Project Queues to allow agents who belong to multiple helpdesks to see all of their issues. We also encourage the use of…

Thanks for the input. Unfortunately, it doesn't work because I need to send the email as soon as possible upon creation, without waiting for an agent to change the status. I have come up with a different solution, which is to create a scripted job that watches for the newly created issues and, if the form is attached, then…

@Bill Sheboy Thanks for the suggestion. If you don't have an SLA, then you would need some way to track time in status, right? One possibility is to have a date/time field that you populate when the issue enters "Needs Attention". Then your timed trigger could compare the time to the current time and decide whether to send…

I voted for and watched this ticket. It is frustrating that this capability is not yet available in the Cloud.

There is a recently created Jira Cloud ticket for this: https://jira.atlassian.com/browse/JRACLOUD-76982 - Unfortunately, I doubt that Atlassian will do anything about it

You could use a hyperlink to the profile rather than an @mention. 

I went back and realized that "duh" of course you can use startofWeek(-1d) to specify the previous day. Your JQL is failing because you are calling for "=" rather that >= or <=. Keep in mind that the created date is a date/time field, so = would have to be exactly the same date/time. You probably want created >=…

You want to use StartOfDay(-2) for a report that runs on Monday and returns tickets that were created in the last two days. The number in StartofWeek is the number of weeks forward or backward from the current week. So StartOfWeek(-1) is the start of last week. StartOfWeek(1) is the start of next week. There isn't any way…

One thought is that you could have a filter that shows all issues that have been updated in the last X days. I would then download that into an Excel spreadsheet and run a pivot table by project, showing the count of issues within the selected time period. Projects that are quiet wouldn't show up. If you wanted all project…

You can't - the purpose of @mentioning you is to force an email to you. If you could turn it off, it would defeat the purpose.

This is an interesting idea and I will have to think about it a little more. Thanks for suggesting it.

I will have to think about the validator function. I could test whether the actual step would succeed and notify the user in the transition if not. @Nic I understand what you are saying about not have scripted post-functions that fail and leave the ticket in a unstable state. However, it would be possible for a decent…

Running a very simple test: assert 1 == 0 causes the transition to fail with an ugly assertion message. Not what I want. throw new Exception("Failure message") does not cause the transition to fail. Still looking for a way to cause my transition to fail.