Thomas Deiler_db00h3 Community Champion

Dear @Josh Quintus, you didn't come back, yet. Have you solved your issue meanwhile? So long Thomas

Dear @Georges Alves, please make the question as "accepted", when you found what you where looking for, so that others can profit form this. Thanks Thomas

Dear @t0msk, could you get a route to google? Do you need more assistance? So long Thomas

Dear @Martin Gregory, do you need more help or is the answer fine enough to be accepted? Thanks Thomas

Dear @Jeroen Thoelen, your issue s solved? Do you need more help? So long Thomas

Dear @manitgl, you didn't come back, yet. Is your problem solved meanwhile? So long Thomas

Dear @Luan Minh Nguyen, was my answer helpful? Do you need more support? So long Thomas

Dear @Mauro Biscotti, you didn't come back, yet. Have you solved your issue? Do you need more help? So long Thomas

Our answers where overlapping ... Then you can only do this: Go through all issue and "collect" the options. Ok - if one option is never used - you will miss it. Alternatively you can GET https://server.de/secure/admin/ConfigureCustomField!default.jspa?customFieldId=12303 and parse the HTML response. So long Thomas

Ah! Now I got it: You want to list all option of one custom field, right? This is not possible with the current implementation of the REST API. There is no call for this. For the customFieldOption call you have to know the id, but it is at all returned when querying an issue. Probably you can do this with this…

Dear @Mikhail Kislovskiy, I ust pereformed https://server.de/rest/api/2/customFieldOption/10300/ and got {"self":"https://server.de/rest/api/2/customFieldOption/10300","value":"xyz"} With which call did you get the data of the upper JSON tree? I want to reproduce what you did. So long Thomas

@Frank Schmitz, that sound's odd. The file is part of the Jira installation, you removed. The methods of mail-1.4.1 get overwritten by javax-mail. But why does Jira request for the old jar file? Or why is this recommended? Are you sure, the whole mail functionally works now as before? Javax-mail was used by Jira, for sure!…

Ah, the accept button is hidden, when you hover the mouse some pixels left of the "votes icon", its there ;)

Dear @Mariano Galán Martín, this is the same, if you would recommend a person, who want's to drink coffee from a cup that is 2 meters away, to take a straw to drink the coffee from the distance. Yes, technically you can do, but it is better to tell the person to make two steps forward, lift the cup and drink. So long Thomas

Dear @Tummala, glad, that your problem is solved. Anyway, if you found my support useful, and it could be also useful for others, please "accept" the top most answer. Many Thanks Thomas

Dear @Michael McGinley, is then my answer good enough to get "accepted"? Many thanks Thomas

Dear @Beverly Bricker, I understood your explanation. I recommend to ignore the due date if your users work in an agile board for the reason you explained. When the planning changes you have to fix the due date, on and on. Automatically all issues have a due date - that's the end of the sprint and stored in the entity…

Dear @Biju Oommen This is a known issue (JRASERVER-40911). You can do some port mapping with a proxy meanwhile, until the issue is resolved. So long Thomas

Dear @techKp, this is not possible out of the box. Jira would need a custom field type "Fibonacci". But follow this old post - there is a solution described. So long Thomas

Dear @Mikhail Kislovskiy, somehow you do an API call. I would really like to help you, but please explain a little bit more. Which call did you perform to receive the upper JSON? Which result do you expect? So long Thomas

Dear @Beverly Bricker, this can be for sure done with a groovy script. But why do you need to set the end date of an issue to the end of the sprint date, when using the agile board? This means, you are keeping information redundant. So long Thomas

Dear @Mark Grandau, first - disallow delete issues. This permission is only for administrators, in my point of view. When exactly happened what you described, then I would judge this as a bug. Deleting an issue may not automatically delete sub-issues, there should be at least a dialog. So long Thomas

Dear @Shaan, was it "None" or not? So long Thomas

Dear @Mayank Koli, I have no xp with this python lib. The title of your question suggested, that you know what to do in Python. So long Thomas

Dear @Ankit Patel, the groovy compiler cannot find the class java.util.SimpleDateFormat. I do not know the details of your build environment, but I guess that there is for sure some documentation how to import native Java classes. So long Thomas

Dear @Anne Warmer, if your users, for example use in Confluence the Jira macro, the auto-complete mechanism will only suggest issue, they are allowed to see. If you open both Jiras for all and also the the projects have the same key, it could get crazy. So my advice for the future - merge both Jira instances and separate…

Dear @Monika Frolova, when you change a workflow you can make a backup of the wf before taking the modified workflow "live". But in this step, Jira doesn't save the history of the workflow. You can save it manually by storing the backups, but you will not see the differences. What you could do, is to export the workflow as…

Doppel Top!!!

Dear @Anne Warmer, the app links are in both direction available for all spaces and all projects. This you cannot restrict. But you can restrict projects and spaces, so that even someone sets a link, somebody else cannot follow. So links inherit the permissions from their projects (Jira) and spaces(Confluence). So long…

Dear @Nanda Bhombore, most probably the Notification Scheme is configured to send less mails. Or the mail server doesn't send the mails. Do other colleagues receive Jira notifications? So long Thomas