Derek Fields _RightStar_ Community Champion

Are you looking to manually maintain the list of features for each team? If so, you can create a "Project of Projects" that has an Issue for each feature that each team is working on. This can be shown on a Kanban board. You could also show the features across teams using a JQL filter such as project in (Project1,…

What do you mean by "a format I can parse?" Do you want to execute the JQL via REST? if so, the call would be https://XXX.com/rest/api/latest/search?jql=XXXXX This will return the list of issues that matches your JQL. Look at https://docs.atlassian.com/software/jira/docs/api/REST/8.10.0/#api/2/search-search for more…

First, if you have a production down incident, you should not be using the Community. You should be opening a ticket with Atlassian and indicate that your system is down. That said, have you tried a locked rebuild of your indexes? 

In that case, you need to figure out why the rule isn't being executed at all. Obvious things to check are that it is enabled and that it is set on the project. Not sure how much else I can tell you without getting in and looking

Have you checked the Automation Audit log to see whether the rule was executed? If it is not executing, then you have to figure out why not. If it is executing but no email is sent, then you have a different problem to look at. I will often put the "Log Action" action into my rule so that I can see something in the log…

In that case, you can create a new Event called "Moved to Code Review". You would set the notification for this event so that it notifies the Project Role "Team Lead". Raise that event on the "Submit to Code Review" transition. 

Are there multiple Team Leader roles or does each project have a Team Leader role and a person in who is the Team Leader? How do you know which team the developer belongs to? 

You can't have ae Request Type that doesn't have a Summary. When the user clicks on a Request Type in the portal, they are telling Jira that they want to create a ticket. Every ticket requires a Summary. You could embed the FAQ URL in the help text for the Request Type or on the portal page. It might help if you could…

My guess is that Squad is defined as required in the Field Configuration for the project. You need to add it to the Create screen for the Bug issue type

There is a column that you can add to your searches that shows a list of all linked issues. You should use the issue linking capability.

You have a field named "Squad" on your Issue that is a required field. You will need to submit a value for that field in order to create the issue.

@Philip Kroos - TEAM XALT Welcome to the community. I agree with @Hernan Halabi - Elite IT Consulting Group answer. Looking at your board, I wonder whether your workflow is the root cause of the problem. For instance, the Done column seems to being using Status instead of Resolution to capture why the Issue is Done. For…

@Mikael Sandberg Thanks for the tip. I will look into it. 

The good news is that this message is customizable. Go to the Project Settings in your Service Desk project. Under Customer Notifications, you will see a list of notifications. You can edit the text of each one individually. You can also edit the footer text that accompanies each message by editing the template in the same…

I don't think that this will provide the answer that the OP needs. My reading is that he wants a list of all issues that are linked to another issue with "Blocked By" and the linked issue is not done. This is effectively a sub-query, which is not supported by Jira out of the box. You would need ScriptRunner, which provides…

I believe that the calculation only occurs when the value of the field is requested. If the field doesn't appear on any screen, then there is no cost to having the calculated field in the system. When you request the value, for instance in the Issue Navigator, the calculation is done in real time as the data is presented.…

What happens if you uncheck the "Only include issues that have changed..." box? It seems to me likely that none of the 7 issues that were found by the JQL have been updated since the rule was last run.

The list of available Resolution values is set by the Jira Administrator. When the issue is originally created, the Resolution field will be empty. The Jira Administrator will have to update the workflow to add the post-function to the transition that would set the Resolution.

This is the entry that you will see before the user has logged in. Until the user identifies themselves by logging and a creating a session cookie, Tomcat has no way to associate the call with a specific user. You need to treat these as anonymous users. You could look at the following lines in the log correlating them by…

You can't update the Resolution field directly. You need to create a post-function in the transition that will update the Resolution field when you invoke the transition. If you have issues that are "Closed" but have Resolution = Empty, you need to create a new transition from Closed to Closed that will set the resolution…

This is how ticket creation works. It pops up a dialog box with the Create screen. Once you have created the ticket, you will see the new View/Edit screen

Your question isn't clear, but let me try to answer what I think you are asking. The Resolution field is what tells Jira whether an issue is Open or Closed. The name on the status has no bearing on whether Jira thinks the issue is Open or Closed, only whether the Resolution field has a value or is empty, which is shows as…

@Martin Gypser Please send me an email directly to derek.fields@rightstar.com and I will grant you access.

The details of how you implement this are going to depend on the types of fields that you are using. From your pseudo-code, I am going to assume that all of the fields are select lists of some type If my assumption is correct, the following should work for you import com.atlassian.jira.component.ComponentAccessor; import…

@Aayush Mohanka - Could you add a new Custom Field "Static Message", add a default value of the text that you want it to say, and then put it on the screen? You could make the field read-only so that it can't be changed.

You can't do this in Jira without a plugin. Scriptrunner has a JQL function called dateCompare that will allow you to compare two dates with a range between them. https://scriptrunner.adaptavist.com/4.3.1/jira/jql-functions.html#_datecompare This will allow you to write JQL: issueFunction in dateCompare("", "RWE> RWS +2h")

The Reporter must already exist in Jira. This is true whether you create the user via the GUI or REST API. You need to create the user first (can be a "customer") and then create the ticket on their behalf. We are doing exactly that in our environment. We are creating an outboard email handler that will check the email…

Instead of using a password in the cloud, you need to generate an API token and use that as the password, following the same logic as above. You create an API token by going to your profile and looking under Security. I am not an expert in OAUTH implementation. It requires a web server on your end to provide the user with…

You can still use basic authentication. You need to pass a header that is Authentication: Basic <base64 encoded token> The encoded token is formed by taking the string <username>:<password> and base64 encoding it. You can do this in Powershell with following: $Text = 'username:password' $Bytes =…

I don't understand the question. When you access a REST API, you need to authenticate, either through Basic authentication or by following the OAUTH flow, which requires a login sequence through a URL. The login credentials that you use will indicate the user that is making the REST call. On server, you could write a…