Kai Becker Community Champion

@Munish Thakur could you try to make a call via another tool or terminal command like curl. It is a little hard to debug, but I guess there is still something wrong with the authorization.

@Trevor Overstreet by default there is no option to store such data in Jira. So this data should be made accessible via app or you could use Assets to store this information. But therefore an upgrade to your Jira plan would be necessary.

In addition, check the attached screenshot for a reference regarding authorization:

Hi @Munish Thakur could you please make sure, that {{ProjectKey}} has a value. You could use log action to push the value of the variable to the audit log. And could you make sure, that you have provided valid credentials with your request. If you are not identified correctly, that the api will not list any projects and…

Hi @Benjamin Dains easiest way would be to check the database. Thats how we usually handle these filters. The corresponding table would be "searchrequest" SELECT * FROM searchrequest WHERE reqcontent LIKE '%issuetype = Bug%' OR reqcontent LIKE '%type = Bug%';

Hi @Trevor Overstreet I've read your text twice but I actually have no idea what you are trying to achieve. Out of the box, there is no option for Jira Cloud to pull data from a database. Therefore you would need to use an app like Elements Connect

Hi @Jehona Eslais taking a quick look, it seems that your customers are getting the wrong emails. The first screenshot looks like a jira notification, but instead an external user should get a customer notification. Are you using a third party app? Looks a little bit like email this issue? Looks like there is a…

Hi @Munish Thakur welcome to the community. Could you please give some more information? What is the exact call? Do you use a certain app to send the request? 

Hi @Filip Hanaczewski welcome to the community. I'm not quite sure what you are up to, as you selected cloud as deployment type but ask for a database field, which will only be accessible on Server/DC. Anyways, to get the request channel type, you could base your request on the following: SELECT p.pkey || '-' ||…

Hi @Durell Demartini in my opinion it would be a better idea to store this file on a separate server e.g. webserver or a file sharing service like Dropbox / Google Drive / ...

Hi @dieManu welcome to the community. If I'm getting it right, what you are trying to resolve is an object from objectType a being an attribute of another object b. If that is right, than this is totally possible. It would look something like this: You can see the more complex setup in this graph: Hope this helps.

Hi @Sue Lund as of now, there is no other solution than copy&paste. The feature canned responses is currently in development, so that might be something that will make your life easier in the future. But for now, you will have to copy&paste

Hi @sandosh.vaidyanathan3 what is your question? What are you trying to achieve? 

It might have not been rolled out to your instance. I just realised that this feature is still in beta. The migration settings should be here: <site>.atlassian.net/jira/settings/system/migration/dashboard An alternative would be to use a third party app (configuration manager for example) or do it via CSV ex- and import.

Hi @Matthew Knab yeah I got that, but thats fine exactly what I meant. User and date fields are always added to the right side of the issue, no matter where you put them on the screens. There is an open request to relocate custom fields of this type: https://jira.atlassian.com/browse/JRASERVER-35596

@lapacquah_bryant yes thats what I meant. I had a more linear workflow in mind, so it wrote parallel path 🙂

Hi @Alya Melati Putri this is not possible, but you could default to sharing with the organization via the global JSM settings: <your url>.atlassian.net/jira/settings/products/jira-service-management-configuration Should new requests automatically be shared with a customer's organization?

Hi @Pankaj Sinha issueLinkType = clones should do the trick for you, in combination with the list of issues from your software project.

Hi @Matthew Knab the issue view is correct, corresponding to your screen settings. The problem with your fields is the following: * Components --> are always shown and can't be removed via screen * Labels --> are always shown and can't be removed via screen * Start date --> it is a date field and therefor always located in…

There might be useful gadgets in other categories as well, but having an eye on foreign names or types should help. The gadget you had previously is from a 3rd party app. Your choice should be the "Filter Results" gadget I guess.

Hi @James Mason welcome to the community. Scriptrunner Cloud is a little bit different than server. You need to use the REST API to get the data you need. Maybe this script will point you into the right direction: https://library.adaptavist.com/entity/sum-custom-field-related-epic-issues?tab=cloud

Hello @Rachel Jones welcome to the community. It looks like you have selected the wrong gadget. If I understand you correctly, you want to populate a Jira Dashboard gadget with a filter you just created. But your gadget title reads Projectrak in it. So I think this was a mistake and this gadget does not allow Jira filter…

Hi @David Fang welcome to the community. It sounds like you are trying to achieve a cloud to cloud migration. There is a detailed step by step documentation that can be found here: https://support.atlassian.com/migration/docs/perform-a-cloud-to-cloud-migration-for-jira/

You're welcome @Karoline Rezende Ramos :)

Hi @Lena Sargsyan you could probably take a look at <your Atlassian instance>.atlassian.net/secure/admin/ViewStatuses.jspa and look for Review statuses, to identify where they are from. They could also have been created but are not in use in any workflow. Regarding the numbers, you are right. They are generated by the…

Hi @Mike Clarke , this is indeed possible, but a little bit of automation magic is needed 😉 When creating a project, you could use the smart value {{project}} and get the id from it via {{project.id}} We can now use this id to query the Jira REST API and get the style (next-gen or classic) of the newly created project. The…

Hi @Wolf Elkan , welcome to the community. Could you please post a screenshot of the rule, so that we can better understand the current setup?

Hi @Lena Sargsyan , I guess you have several team managed projects with review status in their corresponding workflows. Because of that, you have these duplicate Review entries with different numbers.

Hi @Grace Dehergne , I haven't had any customer instance so far, where deleted issues still show up in the database. How do you still find these deleted issues? Are they still persistent in the jiraissues table? Do you use a Server setup or a Data Center setup with multiple nodes?

Hi @Sreenadh it is quite hard to analyse this problem with just a screenshot. Could you open the browser console an check for additional logging?