Derek Fields _RightStar_ Community Champion

Were you able to find a fix for this? We are experiencing the same problem.

You are correct. It isn't that difficult. There are three levels of security in Jira and you need to understand them in order to make what you want to do work. 1) The first level is the User. They are your base. They are able to access your Jira site because they belong to a Group that gives them access. Typically, this is…

It has been quite a while since I posted this. Everyone is correct that there is no current way to import .ics files to populate the holidays in Cloud. At the time that I wrote this, I was working almost exclusively in Server. Now that we have migrated to the Cloud, we are also in this unfortunate situation of having to…

You will need an app like Email This Issue to enable custom email formats. 

I think that this would be easier to accomplish using Automation for Jira. That said, it should be pretty straightforward. You can find example code for creating a sub-task here: Example Custom Scripts (adaptavist.com) All you need to do is to start by getting the value of the "task creator" field and then loop through the…

@Bill Sheboy - We haven't been running it long enough to see any race conditions. The Re-Fetch suggestion is a good one and I will incorporate it. @mararn1618 _secretbakery.io_ As I indicated, the solution isn't perfect. The subject line of the emails would have to be virtually identical for the JQL to find what are…

Filters are a simply copy/paste. Bring up the filter in the Cloud, copy the JQL and paste it into the Issue Navigator on Server. There is no way to do that with Dashboards. You have to recreate each one manually.

Short answer is that you can't with resorting to the REST API. The following REST API will return a paginated list of filters, with their JQL: https://<your-site>.atlassian.net/rest/api/3/filter/search?expand=jql You would need to run through all of the returned records looking for "epic-125" in the JQL.

What is happening is that there are two events occurring. One event removes the old value. The other event adds the new value. So, when the new value is being added, the "oldvalue" is null. Try something like this (I haven't tested it): def changes = event?.getChangeLog()?.getRelated("ChildChangeItem")?.findAll {it.field…

Here is a start. You would install this as a Script Condition using ScriptRunner. import com.atlassian.jira.component.ComponentAccessor; final String LINK_TYPE = "DUPLICATE"; final String ISSUE_TYPE = "Initiative"; def linkManager = ComponentAccessor.getIssueLinkManager(); def links =…

I will anticipate the response by Agilists and tell you that no one should take credit for unfinished tasks in a Sprint. If you can't finish the Story end-to-end, then you have finished. Credit is a team metric, not an individual metric. Now, I will get off my soapbox and answer your question. You can set up a Scrum Board…

Set up a quick filter that will hide the issues with that Status. You could also set a date so that you see the newer ones but not the older ones or vice versa

Welcome to the community. Sub-tasks are different than linked issues. If you are trying to find all issues that are linked through the "is caused by" link, try this: issue in linkedIssues(<issue key>, "is caused by")

This code should do it for you: import com.atlassian.jira.component.ComponentAccessor; final String permittedGroup = "GROUP"; final String protectedField = "Field"; def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser(); def groupManager = ComponentAccessor.getGroupManager(); def valid =…

Charles - welcome to the Atlassian Community. If you are asking an ITIL-oriented question, then the answer is that JSM comes with a pre-defined workflow for Change Management. However, in our experience working with numerous clients, there is always configuration that needs to be done to implement CM the way the client…

What do you want to know about the user? You need to provide some more details about what information you want to view.

You need to pass in the Authorization header as part of your wget call. For Bitbucket, you need to create an application password from your Profile. Then with wget, you would call wget --http-user=USERNAME --http-password=PASSWORD where USERNAME is your bitbucket username and password is the app password that you created.…

Your script needs to be able to access the files. You may need to SCP/FTP them across from the remote server in order to attach them to the ticket. 

You can also use the creator field. The Creator is the actual user who created the ticket, not the Reporter, which can be changed. creator = jeff will show you all of the tickets that you created, regardless of who the reporter is.

don't use now(). just write "dueDate > 30d" 

This is not currently possible in Cloud.

Adding on to @Alexis Robert answer: Once you have added the customer to the Service Desk Customer role, you will be able to set the Reporter (the originator of the ticket) on the Create Issue screen. You will need to make sure that Reporter is a field on that screen (it usually is). A better approach that we advise all of…

The proxy server is definitely set up to forward HTTPS correctly. All of the other URLs that are invoked by the page are using the same HTTPS base url, so it is not a scheme or SSL problem. It is something specific to these URLs that are not being called or handled correctly. I have checked that long URLs are supported.…

What do you want to be different between the two boards? By default, the Kanban board will reflect all of the issues in the project. If you want to show only a portion of the issues, you need to create a filter and base the board on that filter instead of the project.

There is a plugin - Issue Templates for Jira - that will allow you to create pre-populated templates that you can use. Two other alternatives: 1) You can populate the description field with the text that you want in a Create post-function. This won't let the Requester populate it before creation. You would have to update…

It is either/or - the XML restore will populate the database. If you are staying with the same database and can do a database-level restore, I would do that rather than the XML export and import. It will be easier and less prone to error.

You can see the top components on a Dashboard by using the Issue Statistics gadget. That is the easiest way. The SQL to get this from the database is SELECT b.cname, count(a.component) FROM jiraissue a JOIN component b ON a.component = b.id GROUP BY b.cname; This will provide the same information as the Issue Statistics…

What does it mean to "file a bug"? Do you want to create a branch when the bug ticket is created? Or do you have something else in mind?

Try this: select a.group_id, a.license_role_name, b.child_name from licenserolesgroup a inner join cwd_membership b on a.group_id = b.parent_name inner join cwd_user c on b.child_name = c.user_name where c.active = 1

I think that you are looking to create a field associated with a Project? Fields are always associated with an issue. You can't have a field associated with a Project unless you add a plugin. Then, using the plugin, you would need some kind of script to update the field.