Thomas Deiler_db00h3 Community Champion

Dear @Frank Kawperwood, unfortunately the response json fields are not fully documented. You will best experiment with a rest client and figure it out. Its self explaining but you have to check once the response with issue information to understand everything. Alternatively you can make use of Jira REST API lib. There are…

Dear @Martin_Kirk, I cannot answer your question, because we as Community Champions are not responsible for the road map of Jira Cloud. Best you raise a suggestion at https://jira.atlassian.com But while you are waiting for the implementation, you can create a couple of custom fields on your own and add them to the screen…

Dear @Sayali Ekhe., best by polling via the REST API. For Java you can use Apache's HTTPClient Lib. Or you fire a webhook when a new issue is created, Then you have to implement a "fetcher" on the selenium side. Anyhow you have to implement the complete logic for this environment creation on a VM. So long Thomas

Dear @Sierra Warnes, what has your question to do with Confluence? So long Thomas

Dear @Siqing Li, have a look at this page. Of cause, you have to change the samples to fit to the Confluence REST API. Here are some more links (Link1, Link2), but you can google more yourself. So long Thomas

Dear @LarryD, I totally understand your need. Unfortunately this is not possible. Best you vote for this issue. The requirement is open for many years. So long Thomas

Dear @Frank Kawperwood, when you search for issues(JQL: status = "In Progress), you can just export them to CSV or XML. Click on the icon in the upper right corner of your screen. But when you pull the data form the REST API, you can get any detail (even the history) you desire. But some coding skills are required. So long…

Dear @Corby Webster, the search for history information is limited to a couple of fields (assignee changed BY thomas OR priority changed BY thomas OR resolution changed by thomas OR status changed by thomas) AND updatedDate >= -1w So long Thomas

Dear @jo astley, I had a case with a customer, that created a custom resolution named "unresolved". So when they took this one, it looked for the user like NONE but not for Jira, Just to be sure that it is not the case for your system ... So long Thomas 

Ok, nice forensic analysis. The RESTClient always worked fine for me. This whitelisting is intersting. I never had to set this or disable. Was it configured before? Are these new default settings? Which Confluence version do you use? So long Thomas

Ok, In your case, I would create a news board that is similar configured (you can delete it later), to exclude a board "error". If the bug shows up in the new, you can start comparing both. If not I would perform a "project reindex". If this does not help, clone the invisible bug and check if its clone is also invisible.…

If bugs in generally are shown than it can be one of the followinf reasons to check * The bug was once assigned to a sprint that has been finished * The bug belongs to a version/component that is excluded from the board filter * It has a resolution * The status of the bug is not mapped to any column of the board So long…

Dear @maarten breesnee, with just Jira you cannot prevent this while allowing the management of versions and components. But your approach with a nightly running script sound pretty pragmatic. With the REST API you can check the users and roles settings per project and remove unwanted added groups. Can be done eg, with…

Dear @jo astley, just to be sure, was that rogue bug once on your backlog/sprint before? So long Thomas

The big one, called script runner. Probably there are others.

Dear @Fubha Burney, with standard Jira mechanism, it is not possible to request something like "give me all issues where the resolved date is not more than +3d from the created date", because you cannot compare two fields with each other. Therefore you will need a plugin. So long Thomas

Dear @AbdelrhmanE, you can perform a GET /rest/api/2/issue/createmeta?expand=projects.issuetypes.fields All fields are returned for all projects where you can create issues with your requesting account. So long Thomas

Afaik, when quering an issue you get all custom fields / system fields, regardless if they are shown on the screen, but filled with NULL if there is no value. You need the knowledge of the create screen when caling the API.

There is a difference - yours is for cloud mine for server. ;)

@Petter Gonçalves, aha, what did I miss in my answer?

Dear @Tobias Brunner (Admin Account), unfortunately I have to agree. With standard Jira this is not possible. There is an Issue that is most closest to your requirement: Locking an issue completely. I just voted for it - you can do, too! So long Thomas

When you go to the settings of your JSD project there is a tab on the left side:

Dear thomas.newton@pwc.com, sorry, but probably I don't get you right. You can, apart from what fields you have configured per screen, reduce/hide the set of fields shown to the customer: So long Thomas

Hey Tyler, my idea is not fresh, but I would do it like that because I can ;) Use both REST APIs from custom code (PHP, Python, Java, ...). So long Thomas

Dear @Pete P, I recommend to do like described in this article (link behind your link). Managing Issues via a User Account That is what I also did in the past. The rules for the dba is then, the first available picks it and assigns the issue to himself. With adding "current assignee" to the notification scheme, the group…

Dear @Justin Ledoux, I know how exhausting development against the rest api can be. I did in Java with Apaches HTMLClient and I got gray hairs while doing it. Anyhow in your situation I would point out following topics for the source of the problem: * Angular Implementation * Jira server configuration (reverse proxy, load…

Dear @Giancarlo Agurto, you are using the words "Request Type" and "Portal" in your question. I guess you are using Jira Service Desk and not just Jira Core, or? You can do this with the Automation part of Jira Service Desk. Create a rule that is triggered on new created issues and when a certain request type (field name…

But what you send with Postman as payload ist not the same you send with your Angular app. What are the two headers like displayed on your screenshot? Btw: the upper json search request seems much to complicated. I recommend simple using a: GET /search?jql=project=RCA And if you make usage of POST cross-site referencing…

What is Express API? Can you increase the verbosity level? What's the error message, when you search for a project, that doesn't exist? If you are familiar with wireshark you could catch both request on network level and compare. I doubt, that they are similar ...

Dear @Justin Ledoux, have you tried to seach with a GET request instead of the POST? So long Thomas