Nic Brough -Adaptavist- Expert

Actually, it is. I suspect you have a different problem.

Ok, but hiding an entry in a list of things you can see doesn't simplyify things for people. I don't think there's any benefits to that. It sounds like you have a wider-ranging visibility problem and a review of who can see what is probably a worthwhile exercise! I'd also consider creating a simple curated "space directory…

There's no screenshot, but the answer is almost certainly that the space permissions do not allow all your users in to see it.

Ah, um, no, because when you say "only the reporter can create", you don't know who the reporter is until after creation, so Jira lets everyone report.

Yes. And I explicitly asked you to run one of the questions as another user, not root, as did Robert.

You will need to talk to your Jira administrators, and ask them to set up a new project for you. I'm afraid you will not be the first in the field to use it, one of my first freelance contacts was helping a university clean up and redesign a huge pile of their projects, including several handling psychometric research…

It was the create screen. Screens can be called anything, it doesn't matter if it was called "scrum default", "bug default issue", or even "not the create screen". The create screen is the screen the project and issue type have been told to use when someone clicks "create issue". It's defined by the issue type screen…

When you say "custom number field", exactly what type of field is it in Jira? Can you go to Admin -> Issues -> Custom fields, find it in the list, and look beneath its name for the field type? What does that say exactly?

We can't see what you are doing with half of those, there's four answers instead of three, and the first answer was to the third question but run for the wrong user. Please, run questions 1 and 3 again, as the users asked for (your long screenshot shows us what you did and the results perfectly for question 2)

Ok, so those permissions are utterly snarfed-up, but in a way that should actually be letting you do what you're trying to do. Only other thing is that it might be the directory, so can you show us * ls -l /opt/atlassian * ls -l /opt/atlassian/jira * id For 1 and 2, do it as root. For 3, as @Robert Wen_Cprime_ said, run it…

No, but there's nothing to stop you making many calls in one process.

Yes, and not just before an upgrade, you can clear it any time. Confluence will just re-create anything it needs. Leave the directory itself there, but feel free to kill all the files and sub-directories it contains. Just make sure Confluence is not running at the time of delete. You won't damage your data by leaving it…

No, comments can only be made on existing items. If you think there's something to add as a comment on a new issue, it probably should be in the description!

I think there's a 99% chance that the files and/or directories are owned by the wrong account (probably root) Can you check the first command when using su or logged in as root?

I get my colleagues to check mine, but I have the advantage of an Atlassian-based consultancy to ask...

What does ls -l /opt/atlassian/jira/bin/start* show us? Also, can you try head -10 /opt/atlassian/jira/bin/startup.sh

Tell them to go to trello.com and sign up - the sign-up start process is the very first thing they'll notice on the page.

Hmm, that looks ok to me. What exactly do you get when you try su - jira

Ok, next checks are what @Stuart Capel - London said - is the user enabled, have they logged in at least once, and are they in the "can use Jira" group? (You can check all of this in one go by asking them if they can login and see the issue you're trying to assign to them)

Ahh, excellent, glad to have got you to the right place!

Out of curiosity, why would you do this? The space directory is designed to be a list of things you can see. Why would you want to break it by removing items from the list?

If they don't have permission to see the objects in Insight, then they shouldn't be running something that could expose it to view. Why not just grant them view rights, as they need to see the data in there?

Ok, that's ruled out a lot of stuff, but we need to look again at question 1 and some of the stuff around it. Can you compare two issues please - one that has this problem, and one that is appearing on the board correctly? Can you confirm the board filter should be selecting the issue, and how the status are mapped into…

Two things to do: Click on your profile icon at the top right and look for "personal settings" in the menu that appears. In there, there's some email options towards the bottom of the page. The other one is a bit harder; I'm afraid you need to talk to your admins about getting the email storm turned down, they'll need to…

Welcome to the Community! Some quick questions: * When you say "only on all issues with status changed properly" do you mean that you've got issues that are in "in progress" showing on the board? And they got to "in progress" by a human using a transition or dragging the card into the column? * Have you refreshed the…

Welcome to the Community! You will probably need to talk to your administrators about getting the right access to the system you are trying to work with. We're a community of people here to talk about Atlassian, we help out when we can, but we're not the administrators of your system (We don't know what Jira your FICO…

Welcome to the Community! The "take a moment" message generally does mean the rather vague English term "a moment" - it should be a few seconds, which could stretch to an hour if you're doing something very English like queuing and you're told "the bus/attendant/doctor will be with you in a moment". In Jira though, it…

Yes, whatever is calling the API will need to know where it has moved to. (I'm assuming by "product url" here, you mean the base-url of your Jira system - you're changing the name from abc.atlassian.net to xyz.atlassian.net for example. If not, then can you explain more about what you mean by "product url"?)

Most of the Atlassian applications do actually leave the old versions lying around when you upgrade the apps or even remove them. Most of the time, it's harmless, they just take up a bit of disk space, and people like me do a bit of housekeeping the next time we do an upgrade of the application. But re-enabling them…

That's of no relevance to who should report it. There's no point in me reporting it - the Confluences I've got admin on (and also the ones I do not) don't have this problem as far as I can tell, so me reporting it would be a waste of everyone's time.