Thomas Deiler_db00h3 Community Champion

Dear @Ethan Murray, I have no sample customers at hand, but anyway that depends how sensible your data is. Financial = money transfer, customer profile information, ... So long Thomas

Dear @., what you are most probably looking for is a Slack Bot that connects to Jira. For this follow this link or search the web. The Jira project needs then to be configured for Discard/Accept. The Slack connector will help you in the other direction. So long Thomas

Dear @Will O'Dwyer, normally I do not recommend plugins, but in this situation you have to evaluate the tripplet of: * Automation Lite fo Jira * Better Excel Export * Automation for Better Excel When you do not like to get another dependency to a paid plugin, you could do this on your own with the REST API and some custom…

Dear @Mitch Wiemans, it seems that you have found a sanity bug in JSD. It should not be possible to delete custom fields, when you cannot remove them later manually from the configuration. To fix this, I fear that you have to reconfigure your affected project from scratch. But before try to run re-index and integrity…

Dear @Haresh Devaliya, 1) have you tried to expand=*all when you pull this data 2) its possible, that the REST API lacks this kind of information So long Thomas 

Dear @Anupama Singh, you mean SSL certificate, or? When using Jira Cloud, you don't have to care about such things - thats the service you pay for. So long Thomas

Dear @Aravind, this is not possible over the CSV import mechanism. You have either find a plugin that suits to your needs or you do it with the REST API (and some custom script code). So long Thomas

Dear @Marek Ochab 1) Nothing will happen to the internal user accounts, they are just overlayed. This works only if the user name matches. In the end you have a fall back solution. If LDAP is down, Jira waits for the timeout and then asks the internal directory. So important message: Never place you admin account on LDAP,…

Dear @Robert Hölzl, the browser is "partially" usable. Best you download a browser extension like "RESTClient". There you use "basic authentication" and add as custom header "Content-Type: application/json" when POSTing data to the REST API. So long Thomas 

Dear @Sunil Kumar, sorry for the delay. When using the rest api, you have to pass your credentials with every request. The method is called "Basic Authentication". See this link. Of cause, you can also check out OAuth. So long Thomas

Had a look to my second post?

It can be the result that LDAP replies "no" to Jira. It has nothing to do with the API, what I guess. It's LDAP that sometimes says no instead of yes.

Dear @Anne C, application links are designed to work across several versions of Atlassian products. It can be expected that they use internally their REST APIs to communicate. The APIs are most time downward compatible. This means "Yes, 5.8 will work with latest Jira." But: regardless what is written elsewhere, as an admin…

Dear @Robert Hölzl, this sounds like something spooky. But in the end something must have changed in your system. Either: * Jira Version * Firewall * Operating System update * Network * SSL Certificates * etc ... Can you find out, what change has been made since the past week? So long Thomas

Dear @Meenal Khurana, just a rough guess, but eventually the LDAP is the reason. If there is a limit configured, to many equal auth requests could get denied. I recommend to increase the log level of the LDAP managing class to DEBUG and also check on LDAP side what happens during the mass requests. So long Thomas

Dear @Maali Albalt, have a look at the upper articles with "history" in the summary. Everything you need to know about one status change can be found in the issue history. So long Thomas

Dear @Wisam Abdelaziz, best you remove both links and re-create them. When using self-signed SSL certificates, make sure, that the JVM(s) "knows(know)" them. Otherwise the applinks will not work. See this troubleshooting guide from Atlassian. So long Thomas

Dear @the_bisa, I doubt that this is possible with JQL (without custom plugins). I would do this with the REST API: * get all released versions from project (remember their releasedDate) * get all bugs of a project and compare the releasedDate with createdDate of the issues So long Thomas

See this post.

Try this: * Stop you new Jira * Empty the JIRA_HOME directory completely * clean the DB (drop all tables) * Start Jira and configure the new DB (no XML restore) * Stop Jira * copy only the 3rd party plugins into /var/atlassian/application-data/jira/plugins/installed-plugins and not those jars, that came with Jira * copy…

Did you use the same JIRA_HOME as with the old DB?

Dear @Ash, it's possible to manually install more than one DB of the same type on one system. My thought was, that there are two different versions installed. But you exclueded this. Then lets check your process for the migration (my assumtion): * Backup data to XML * Stop old instance to prevent data modification * Setup…

Dear @Karen, the answer will give you this page. So long Thomas

Dear @John Landers, how you describe this sounds more like a discovered bug. But before contacting the support: It is possible, that columns that contain no data are skipped while exporting. So probably the first 1000 issues had at least one entry in a particular custom field but none of the next 1000 issues had any entry…

Dear @Sunil Kumar, everything you need to know is written in this article you listed. You need some coding/scripting skills to finish you task. This can be done with PHP, python or perl as well as with higher programming languages like Java. Following this link will give you an idea, how to do with python. So long Thomas

Dear @Savita Datawade, what you describe is not a standard functionality of Jira. Seems that you are using a plugin like Zephyr. Please provide more information (eg screen shots) about your problem, so that the community can help. So long Thomas

Dear @Wisam Abdelaziz, are the application links between both servers work correctly? So long Thomas

Dear @Reinhold Füreder, appart from your described problem, you cannot directly open a bug any more. You can just create suggestions. To raise a bug you need to contact the support. They will then verify and if valid, create a bug. So long Thomas

Ok, then something went wrong when exporting the data. The XML dump is free of any DB flavour. It would make no sense to export DB details in an XML file. Otherwise you could just dump the DB without Jira. Just to double check - when you reimport into the same DB type, does the error occure, too? Another source of the…

Dear @Derek Pence, nope - I don't think that there is a plugin that supports "your database" (which one is it?). In the end It is not a good idea to let Jira DB talk to another DB. Never write data ito Jira DB on your own - always use the REST API. You could write a simple middleware app, that is awaiting a web-hook call…