Comments
-
What does the log file say the server is doing? Or what is it failing on?
-
I am afraid the question is not clear. You "log" a "ticket" in Jira by pressing Create, which takes you to a create issue form to fill in. You will need to explain the question more if you are struggling with "create issue"
-
CSV is text, so just open the CSV and edit it. You'll find it easier in a spreadsheet though.
-
The documents @Yoga Reddy {Appfire} gave you cover how to install it, including connecting it to a database. Could you explain what part of them you are not following?
-
Make sure your sub-tasks have a different workflow to the parent issue type. I know that sounds odd, but what you're trying to do is not possible with just permissions, you have to do it in the workflow. The permission scheme just controls access at a project level. You'll still want it to let everyone comment on issues.…
-
Permission to delete is handled by the space permissions. Most admins set them to disallow by default, as people often delete things they really didn't want to (admins can fish them out of the bin, but when you're doing that dozens of times a day...)
-
That is intended behaviour - Confluence is not supposed to allow duplicate page names in a space.
-
It's off by default because it's usually a bad idea to let people delete Jira issues. As soon as you've confirmed a deletion, the issue is gone. These forums are rammed with questions about restoring deleted issues, because people have been allowed to delete in error. Restoration is a nightmare at the best of times, you…
-
I default to using the methods Atlassian recommend in the docs - replicate the attachments and installation to another server, and take database backups using the database's standard tools regularly. There are variations - mounting the attachments directory on shared storage, not bothering to back up the install relying on…
-
You can turn off relative dates globally - see https://confluence.atlassian.com/jirakb/disable-relative-dates-in-jira-applications-414187622.html
-
I'm not seeing a bug here, all the evidence shown so far is that the boards are not set up correctly. (and I'm not an Atlassian, so I won't be looking at it)
-
The only thing you can do in Jira would be to code a validator that you could put on the "create" transition that blocks issue creation if it finds a duplicate. This has a weakness in that there's no way to go back to the user and throws away all the data arriving.
-
That's no problem. The problem here is that the certificates you have installed are not valid. You'll need to install valid ones.
-
The indexing system that Confluence uses explicitly states that it does not work on NFS and other shared file systems. You must use a standard one.
-
Groups don't have a field that shows any form of status like "done". Could you explain what you are actually looking at?
-
>Gee, thanks for nothing. There is no "Time Tracking section". Yes there is, if time tracking is enabled and in use in your project. Have a closer look at the config.
-
The easiest way is to look at the layout - are the main menus across the top of the screen (Server) or on the left-hand side (Cloud)?
-
I get grumpy when people ignore what has gone before. Your statement is, as shown above, wrong. Please don't be rude to people who are trying to show you where you are wrong.
-
>Hey Nic would you be able to elaborate on why Atlassian thinks they are following the Scrum way by not doing this In Scrum, an issue is done or it is not. Partially done does not matter, did you deliver the issue or not? Estimates on sub-tasks are utterly irrelevant to that question, because it doesn't matter if 0%, 1% or…
-
>I was trying to get the confluence data directory mounted from a nfs share. Ok, there's a problem. Parts of the Confluence home directory should never be put on an NFS share as they simply do not work on NFS. You need to move the home directory on to a standard non-shared file system and try again.
-
I would remove your database access. You don't need it, because you do not want to use it to do this. You must never write to an Atlassian database when the application is running, because you will, at best, make what you've written useless, and at worst, lose everything. Forget the database, write your code to push your…
-
Confluence doesn't have "issues", and you labelled this with Confluence and then talked as though it was Confluence. My best guess now is that you really mean Jira, where you need to be granted "delete issue" in the project's permission scheme. Jira admin is complex because Jira is powerful and flexible - that's the price…
-
We don't know, you have not told us what you have, what you have configured or what is actually slow. Take a look at the configuration of a "slow" transaction - what actually is slow? Page load as it refreshes? Or the actual transition processing? What processes are running during the transition? What are the validators…
-
Look at the project permission scheme - this tells you who is allowed to delete issues in the project.
-
Ok, go to search and search for "project = Y". Save that as a filter, then go to your dashboard. Add a "filter statistics" gadget that uses your filter and groups by version. This will give you a list of versions in the project with a count of the issues in each one. It will report current numbers when you refresh the page.
-
Amend the board filter so that it includes the issues you want to see on the board.
-
Why are you doing this instead of just following the doc you link to in step 9?
-
The "child pages" macro does this.
-
On server, your server's administrators can edit the robots.txt file.
-
That usually means the network is unavailable. You'll need to look at the network setup. All the rest of the log around that error could well tell you a lot more.