Comments
-
And also all files within? And same for confluence HOME? If you have meanwhile started confluence as 'root' the file permissions could be switched back to root, for some files.
-
Dear @Gamesys, you have to expand the history: /jira/rest/api/2/search?expand=changelog So long Thomas
-
Dear @Frank Lienhard, have you tried the org.apache.log4j.RollingFileAppender? See also this. So long Thomas
-
Dear @[deleted], as @Grzegorz Lewandowski wrote - this could not work. Be very careful and backup before. Again - this is at your own risk. So long Thomas
-
Dear @Londa Liau, the error message could be an indicator, that the user 'www-data' has not read/write permissions. As something seems weird, first, do you have the system user 'www-data' at all? Have a look in /etc/passwd. Then check if the files in Confleunce dir are owned my 'www-data'. So long Thomas
-
Dear @Andrew Golodyaev, the user in this post has the same error message like you. Does this article help you? So long Thomas
-
Dear @Grzegorz Lewandowski, good to know - I did it once (some years ago, if I remember right) and it worked for me. so long Thomas
-
Dear @[deleted], you can do this at your own risk on replicating the file structure in your file system. But shut down Fisheye first. So long Thomas
-
Ah sorry - switching back and forth from one question to another, i mistakenly wrote Jira. You can take the same script but name it different. Confluence is started the same way as Jira. I appologizes Thomas
-
Or you start you hierarchy with a Tale, but it's just naming.
-
Dear @Shawn Smith, you can check out the Email functionality extending plugins on the marketplace. If you nothing is suitable, you can post process your news incoming issues over the REST API. So long Thomas
-
Dear @Florian Obradovic, Jira has not the same focus on writing good looking text as Confluence. What yo can do is search for "rich text" plugins on Atlassians marketplace. Eventually they understand Confluence markup language. So long Thomas
-
Dear @Sabine Bamboschek-Keller, how you describe, it has nothing to do with Confluence. It will be a problem of the accessing computers. Please let one of your colleagues log in on your computer and open a Word document. If it works, user restrictions / permissions can be excluded. So long Thomas
-
Dear @Gamesys, the information you are looking for, is stored in the history only, that will not be displayed as a search result. You could query the REST API, to extract the dates, when the transition from 'open' to 'in progress' was made. Are you familiar with the API? So long Thomas
-
Dear @Londa Liau, than your Ubuntu 16.04 is not configured for systemd. It uses the old mechanism. OK. Remove the /etc/systemd/system/confluence.service file. Then follow this instructions. Following annotations: * Your system is Debian like. * Start at Step 6. * Don't create the users 'jira', user 'www-data' instead -…
-
Dear @[deleted], this is what I just checked in one of my experimental boards. Exactly, Released is currently your final status. So long Thomas
-
Dear @Selvaraj Karuppusamy, Delete (Remove),Create and Update are experimental for the Server API. See the API reference. Create and Remove are experimental for Cloud API. Update is not a available. So long Thomas
-
Dear @Frank Lienhard, you have to adapt the log4j configuration. This article will help you further. For details on the config format, you best got to the apache log4j reference. So long Thomas
-
Dear @[deleted], so my advice: set the resolution in status Accepted. Then you burndown goes in this moment down. You can move the issues to 'Released' afterwards. This will not change the burndown anymore. So long Thomas
-
Dear @[deleted], short question for better understanding: ar both columns Accepted and Released final columns, or better are both statuses "Green". And does the issue get striked-through when moving in one of these columns? So long Thomas
-
Dear @Sabine Bamboschek-Keller, when I understand you right, your colleagues want to open the document in Word and save back without uploading again, right? Therefore you need to make the browser plugin WebDAV work, that comes with Confluence. Eventually, some compliance settings blocks installing this plugin, or your…
-
Dear @David Cheong, if you want to find the reason, you have to login via SSH on your Jira server. There you can do the telnet. Eventually, the route is blocked from this host. But you have to check it out, before you you continue. So long Thomas
-
Dear @Ankur Dayal, then I have no clue - eventually it is really a bug. Best you contact the Atlassian Support. So long Thomas
-
Dear @Londa Liau, looks like the registering of the service was not done as root. Are you performing the changes as user 'root'? So long Thomas
-
Alternatively to the solutions in the upper reply you can use the "Workflow Toolbox". Please read this description.
-
@somethingblue the similar question are all on cloud.
-
Dear @Dena Bengson, when I understand you right, you don't want to have them as users inside Jira to be notified. You could create a web hook on issue creation. The receiving web server fires then the mail to your extra recipients. Could be realized with a simple PHP or Perl script (server sided). So long Thomas
-
Dear @Manikanta, you can do this with the commercial workflow toolbox plugin. So long Thomas
-
See this.
-
@Matt Koidin reported, that switching off the new experience will fix it.