Comments
-
The rights for doing things should always be separated out. Especially the "view" - an admin with 1,000 projects or spaces doesn't tend to care about most of them most of the time. It's also a security risk, and a nightmare when trying to debug a permission if you're working with an account that "can do everything". Admin…
-
Convert it into a "REST Endpoint" (mostly copy and paste I think), then you can poke JIRA any time you need it to pull back the output.
-
Whichever one of those roles grants "assignable user" in the permission scheme.
-
Site admin gives you admin rights. Delete is not an adminstration task, it belongs to the space. Go to the space permissions and give yourself delete rights, then try again.
-
Check your permission scheme - user2 does not have "assignable user" permission. (Note - do not mix that up with user1's "can assign issues" permission)
-
There is caching that will affect data in macros. If it happens again, then try going to Admin -> Caches. Look for any cache mentioning macros or page data and flush the cache, then retry the pages.
-
Depends on the errors. Might be good to export the space from your server, and re-import it. Exported XML shouldn't carry over the junk from Cloud.
-
A backup import always cleans out the target system, it warned you about it before you committed to it. A Cloud system contains a standardised admin user - sysadmin with a password of sysadmin - you should be able to log in as that and grant other users more rights.
-
For 300 pages and 300Mb attachments, I'd expect the delete to take a few minutes. I'm not sure there's a way to speed it up without a good look into the internals to see why it's taking so long. Does the log show warnings or errors duingthe delete?
-
Ok, so you're trying to move an issue from one issue type to another, one that has a different workflow. This is not a simple task, the only time you can do a simple "set" of the issue type is when the two issue types have compatible configurations. In this case, they do not. Your code is going to need to replicate all the…
-
Eh? I've installed JIRA many many times without a proxy and then put it behind one. Given that these installations are all working fine behind their respective proxies, that statement is demonstrably wrong. Ok, so I've installed it a lot over the last 15 years, and run into the same problems because I still miss stuff, but…
-
Generally, I'll recommend starting JIRA and checking that it responds locally before starting to set up the proxies. But I don't think that would have told you much this time (it would have worked) I think the problem is that you've missed the notes on the protocol - have another look at the red warning panel at the top of…
-
You can't set a status because it's not a field, it's an indicator of the issue's position in the workflow. To change the status, you have to transition the issue through the workflow to land on the step you need to get it to.
-
There's a link in my comment - it should lead you there.
-
To log in as an admin, log in with an account that is in the admin group. To see the server ID, you can look in the log or the database, but the easiest option by far is the licence or system information pages. "Unable to view" tells us nothing more than "you have got something wrong". Have you used the right url? Do you…
-
Follow the "forgotton password" links on the login screens and be sure to click the "unknown email" link first.
-
It's hard to say what might have gone wrong with starting your Confluence. What does the log file say the problem is? (check <confluence-home>/log and all the files in it)
-
JIRA runs on a single "base url", so this won't work. The best you can do is throw up a website with redirects that take people to the right place, but they will still end up on the base-url.
-
There's several ways to provoke this problem, but you've already checked for many of them The ones I'd check over next: * Check that the installer has not done something bad with the database driver - there should be driver in <install>/confluence/WEB-INF/lib * If you have anti-virus, that might be blocking access to files…
-
My best guess is that you're on JIRA 7.2 or above and you have set it up with a MS-SQL Server 2008 database back-end. Is that right?
-
I don't believe Bitbucket has a setting to allow you to do that on the server side. You will need to set up a firewall on that machine that blocks access over the IP addresses you don't want to have it available on.
-
The last version with the old interface doesn't really matter, as the change is on Cloud, and you don't get to choose what version you have on Cloud. The good news for you is that the change has not made it on to Server yet, so you can upgrade to 6.3 and not be affected. From what I've heard, you're probably safe for quite…
-
Your account does not have permission to use the directory. sudo <command> only takes root priviliges while it runs and drops access when the command finishes, so "sudo cd <directory>" will work in that it changes directory, but when it finishes, your normal account is dropped back to where it was before because it has no…
-
There's no migration or changes when you apply a new licence.
-
Nope, it de-duplicates the recipients of the event notification.
-
There are good reasons not to allow deletion of files, you should check with your admins to see if they have any. The two flags for attachment really are just "can add" and "can delete"
-
That's not what you said before, and no, it's not obvious from your points - if it were, I'd have been agreeing with them. I do understand what you think you require, and that's not going to happen. Your real requirements have not been shared, which is fine, but you miss the point that if you don't understand the question…
-
That is odd, I cannot see a single thing that might even be wrong with this. I would check the running system as below and check the -D appears in there (it does not in mine, I've got a single key for a different reason) ps -ef | grep -i jira nic 10681 10666 0 18:41 pts/0 00:00:00 grep -i jira charlie 14058 1 0 Jul02 ?…
-
Only by coding, and most of the approaches to doing it mess up your reports.
-
No. I defined only one single Permission Scheme in my answer. You can work with copies, but I kept it as simple (and flexible) as possible, and worked with a single scheme. The scheme says, in English: Only people in the project role of "Users" can see the project. So, in the comment you've made, you would put…