Comments
-
Dear @Jeneen_DesChamps , when you can exclude that somebody of you users messed up your configuration, I recommend to contact the support. Have a look at https://<yoursite>.atlassian.net/auditing/view, first. So long Thomas
-
Dear @Jeneen_DesChamps , do you use cloud? Next-Gen? So long Thomas
-
Dear @Hyakansha Jukidab do need to create issues from mails in a service desk or a jira core/software project? So long Thomas
-
Dear @Jeneen_DesChamps , the strike-through is an indicator that the resolution of an issue != NULL (unresolved). Regardless of the status you can set the resolution to any value, if the configuration of your project allows this. Good practice to avoid this is, to forbid editing resolution and just let the user select…
-
Dear @dwschulze , first have a look if there is a process hanging (java.exe). Installing as administrator and running as user will lead to problems, because the file permission are not set for the user. Be sure that the user can access all files and has write permissions to jira-app and jira-home. it could be also an issue…
-
Dear @Leeooos , I have no clue about this error message, but in your request there is the parent page missing. This is not documented and was one year ago required to create and update pages. {"id":"169052728","type":"page", "title":"NewPage", "ancestors": ["id":"<the parent page…
-
Dear @Leeooos , yes: 3604482 is the page ID of the page you want to update. Don't forget to increase the version number by one (current page version = 2, then new version = 3). For what is that "python "mjson.tool"? The curl request doesn't require this. So long Thomas
-
This should not be an issue of the SQL Sever. Either the import failed or not. Are there any exception in the log from the DB import? Can you explain in detail what you did? Export of dump on witch version? Then DB switch? Upgrades in between? So long Thomas
-
Dear @Chris , I don't know about this hack but in general all Jira-Server instances are open for this kind of requests by default: https://jira.atlassian.com/rest/api/2/serverInfo This one shows the information of Atlassian's main issue tracking server. You can validate yours, when you point this request to your server,…
-
Dear @Richard_Cunliffe , no you don't. Kanban boards are realized by agile boards. You already have what you need. See this article. So long Thomas
-
Dear @[deleted] , you tagged this question as Confluence. So I assume you mistakenly did this and instead Jira-Server is the right tag. You can deactivate the task by modifying this issue type in the issue type scheme assigned to the project you currently use. See more here. So long Thomas
-
Dear @Ayoub Karaa , for worklog you have to append the parameter '&expand=*all' at the end of you search string. If this doesn't help you have to query each issue again for the worklog with GET api/2/issue/{issueIdOrKey}/worklog So long Thomas
-
Dear @B-CH , please tell us what the log says in the moment of an upload. So long Thomas
-
Dear @Karol Smogo , yep just user status instead of column. Statuses are mapped to columns. When you have a 1:1 relation each column will have its own color. So long Thomas
-
Dear @Ian Bardecki , The Service Desk Team is just a project role introduced with JSD. If not done by you this role is not mapped to a JSD license. Go to Administration > Applications -> Application Access, and ensure that all the people that have to access the upper page consume a JSD license. So long Thomas
-
Dear @Member A -Team IC- , what's shown in the log? So long Thomas
-
Dear @Kamil Beer Affording a Jira license for each and every customer is not a solution either. You do not have to pay for customers - just the agents. so long Thomas
-
Dear @Jiri Pik , I think you have to create a news suggestion for this as https://jira.atlassian.com So long Thomas
-
Dear @Jo Bland , I just verified this on Jira 7.13.5. assignee is EMPTY returns unassigned issues. So my guess is that you created a "dummy" user named "Unassigned" that is aut-assigned when createing issues. Have a look at your user directory, if this one exists. So long Thomas
-
Dear @[deleted] , you can do this with a script using the REST API with following pseudo algorithm: * search for issue with worklogs of olduser (JQL: worklogAuthor = olduser) * for each returned issue do a "Get Issue worklog" * read from each worklog entry matching olduser comment, started and time spent * "Add worklog"…
-
Dear @Jiri Pik , pretty fine. You can do it, it is just not recommended. But then please let us know about the performance boost afterwards. Eventually others are also interested. Eventually this will help measuring the performance before and after: Performance Testing Scripts Jira Performance Testing - Available Tools So…
-
Dear @Jiri Pik following your last link: There is no reason to take any action unless directed to do so by one of our support engineers as a result of a performance issue. So long Thomas
-
See also Error message when updating license key in an updated version of Jira and Update from Jira 8.2.3 to 8.2.4, need to update Core?
-
Dear @Samira Spago , yes. Modifying the keystore will require the java app to reload this information. So long Thomas
-
Dear @Jiri Pik , to be honest In the past 10 years I had never an issue with tomcat and ARP. Either you have a corrupted binary installation or you modified something. Where and when did you get aware of ARP in context with Jira? So long Thomas
-
Dear @Milan Chheda [INFOSYSTA] , yes, as I sad. Jira imports everything that was exported to the dump. Just imagine, some plugins can only be installed via UPM because they are shipped as ORB files. The are normally not available during first startup after an upgrade. When you had years ago a plugin installed, that you…
-
Dear @laurent debaix , you will find them in $JIRA_HOME/log. Logs from insight have different names than the one from Jira. So long Thomas
-
Dear @suresh Raman , please follow this article. So long Thomas
-
Dear @Jiri Pik , this article will help further. So long Thomas
-
Dear @Thomas Annemüller , there is a similar post on this. Somehow I have the feeling that this is a problem of the new release 8.2.4. Please contact the Atlassian support. So long Thomas