Comments
-
Have you used "anyone" in any of the project permissions? I should say I visited while logged in to an Atlassian account, but not one that has any access to your system (I hope!). The page is not leaking - the url says it is a search, but all I get is the header and footer, no data, not even menu options!
-
I'm not sure I would recommend a book for Cloud. The Server books are good to get you going with Jira in general, but Cloud moves fast - if you bought a book on Jira Cloud today, it would be out of date before the end of the year (and given it's December now, you can see I do mean "fast"). You can't stop the rolling…
-
Ouch, no, you do NOT want to remove those files, they exist for a reason. The proxy lines are ok to get it working, but do hint that you may have a poorly configured firewall.
-
That's one of the symptoms of the problems the troubleshooting doc can fix (Mizan pointed to it in an earlier answer)
-
You've got two problems here - OneNote does not have a useful export and Confluence does not have a batch import. You can get around the second one with some scripting, pushing data in over REST or using things like the Confluence CLI add-on, but you need to export the data into a format that can support those.
-
It's as he says. If you want to search several Jira systems for something, you have to log in and search each one of them separately. There is no way to "search across multiple instances" You can link across them, but the search in Jira A is not going to find anything in Jira B, even if it is linked.
-
That does not tell us how you are creating or entering it into Jira. Please explain how you have configured it in Jira?
-
You don't get the "add gadget" option unless you go into Admin -> User interface -> System dashboard. I suspect you are thinking you can edit it from the dashboard view, which is not what the doc says,
-
Have you added your group picker field to the assignee tab? And checked it has the right context (i.e. it belongs to the right projects and issue types when you look at it in the list of custom fields)?
-
Find the <jira install>/conf/server.xml file and edit it, removing the context part of the connector (change "/jira" to "").
-
What do you mean by "space inaccessible"? What is the warning or error? What is the behaviour when a user tries to use the space?
-
Sounds like your MYOB system is broken - a + in an email address is perfectly valid, but a lot of badly written code fails to handle it correctly (before I sound too smug about Atlassian/Trello getting that one right, they fail valid email stuff in other places) There is not a lot you can do about this, other than swap to…
-
Include and include-excerpt. It's easier for you to try them out than explain them. Start by creating a page with just your panel, and a couple of test pages that "include" that page with the panel somewhere in their content.
-
I'd guess the database collation was incorrect.
-
See https://community.atlassian.com/t5/Jira-questions/New-JIRA-Server-experience/qaq-p/632013
-
I guess by "our cloud accounts are blocked", you mean you let the trial expire, and hence the system has shut you out. If it's been over a week, then the instance will have been shut down as well. If that is the case, then there's nothing to "migrate", the Cloud server has been discarded. If you did not take a backup…
-
See https://community.atlassian.com/t5/Jira-questions/New-JIRA-Server-experience/qaq-p/632013
-
You don't. It's already installed. Take a look in the <jira home>/import directory!
-
There's a far easier way to scrub an install back to "empty". Go to "backup and restore" and import from startupdatabase.xml - that will overwrite your entire (working) system with an empty Jira.
-
No, that's what you are paying the licence for. Users.
-
You'll need a bit of code to do this. I'd do it with ScriptRunner as usual, adding a validator with a line for comparison saying something like issue.getAttachments().size() > 2
-
I would not recommend doing that. I would strongly recommend following the upgrade path given in the documentation, and not skipping version 7.0 or 7.1. See https://confluence.atlassian.com/adminjiraserver071/upgrading-jira-applications-802592251.html
-
"not properly working" and "has problem" is useless to us. For all we know, the problem is a penguin chasing you away from the computer if you open firefox or chrome. You need to describe the problem if you want any help with it.
-
The Epic report relies on some data that you only capture in Scrum, and hence would not actually tell you anything if you could use it with a Kanban board.
-
Anywhere you know the line will be executed. setenv.sh is a script that varies by install and settings by site, so they can't just give you a copy, they are relying on you having a basic understanding of scripts Most simple place - insert it into the first empty lines at the top of the file.
-
I'm not saying it doesn't work, I'm just pointing out that it tells you to do the same things the Atlassian docs tell you to do. I can't explain why you struggled with one set of docs and were ok with a copy and pasted version.
-
Ah, yes, I think it explains what I was not getting. You don't care if foo or bar are on the issue, you want to find issues that have a label other than foo or bar. In Jira terms, the starting point is "labels is not empty". But then you want to exclude issues where the labels are only foo, bar or foo and bar. I can't…
-
Hang on, that's not what you asked for. "I want to find all issues that have any label that is not one or more of (foo, bar)" The search "label != foo and label != bar" will exclude those, and all you need to do then is add "and label is not empty". That will answer the question presented. Or is the original question not…
-
/var/www is absolutely the wrong place to install Jira. It's a directory that is used by your web-server to serve up a site. Installing Jira there makes the Jira *application* files available on your site, which is a massive security risk and utterly useless, as well as causing problems with permissions because the…
-
No, the licence model is simple - you allow for X users, and name them by putting them in a group. The people in the group count towards your licence.