Comments
-
>How do I have that all projects visible and avaiable to the ADMIN but for the external client, just limit it to only ONE project? There are several ways to do this, but they all boil down to one simple principle - allow everyone to see external projects but let fewer people into the internal one. Let's say you have Alice…
-
As a non-admin, you don't get a direct view of it. But you can simply look at the list of attachments on the page - is there a delete icon?
-
Do you mean your server has several IP addresses it is bound to and you only want the system to listen on one of them? (I would reach for a firewall over application config for that)
-
That doesn't sound quite right to me. I suspect you're using groups instead of roles. To achieve what you want here, you should have a scheme that says: Create: Role (project admin), Role (developer) Now, let's say we have Alice, Bob and Charlie as developers. Put Alice and Bob into the role of Developer in project ABC,…
-
Yes, sorry. The change of style in the docs for 7 hasn't caught up on google...
-
A lot of my stuff gets blocked with a "unsuitable language or spam" message before I post it. I don't know the rules, but embedding html is definitely one of the big triggers, and chunks of code or logs not far behind. I've just un-spammed your question.
-
It's always of the form below (replace http://hostname with your JIRA's base url - if it's http://myserver/jira then use that) http://hostname/rest/<api-name>/<api-version>/<resource-name> So for JIRA at the moment, it is at http://hostname/rest/api/2/ (e.g. an issue "get" is http://hostname/rest/api/2/issue/ABC-123 )
-
Ok. When you set it up, there should have been an administrator set up automatically, in the internal directory, before you hooked it up to LDAP. This can get a bit complex, because there are a number of possible blockers here: * You don't know that account * It is similar to your LDAP account, so the LDAP account blocks…
-
Ok, that makes sense. Go to Space Admin and check the permissions. Your second user does not have "attachment" rights from what I can see.
-
Ah, that's a really simple one. "LDAP: error code 49 ... data 52e" means "the user you are trying to connect to LDAP with has been rejected because the username and password combination is wrong". It's not the users themselves, it's the account you are using to talk to LDAP with. Check the directory settings in JIRA - the…
-
A scripted custom field won't help - they're read-only (unless sub-step could always be calculated, not entered by the user. Then they're ideal) But I'm pretty sure you can do it with Scriptrunner. I have not tried it myself, hence I'm not 100% sure, but, define the sub-step with values A, B, C, D, E and F. Then use a…
-
I had to assume it is broken because what you gave me is broken. It's not a useful requirement. At least the clarification that you simply want to grab everything from an issue is clear enough to work with. And that's easy to answer. JIRA is already giving you the data it has for an issue in the response. Your application…
-
It's hard to start to tell you how you are getting this wrong. Basically, your requirement is broken. "We want issue data" is not a requirement, it's a statement about part of a process. All of your points (barring the first one about documentation) are obviated by the fact that you don't understand what you're getting or…
-
Is the cacerts file owned by and accessible to the user running the JIRA service?
-
It's the same API and the same call. My guess is that your call is failing because the "do not allow edit" flag is set on the issue you are trying to update. Try editing it in the UI to check that.
-
Every synchronisation requires some resources to run, and obviously, the bigger the synchonisation set, the longer it is going to take. This is generally not a problem for Confluence. The only time I've seen a synchronisation cause performance issues for other users is when it was full of errors. 1800 should be absolutely…
-
The box you are showing there is asking you to select an existing file already attached to the page. There are no attachments yet, so it's empty. Try attaching the file via the attachment link in the menu.
-
Hmm. I'm not sure what that might be. The url looks correct, and there's no reason not to display it. If it were an encoding or "file name wrong", I'd expect a browser error message. I assume the files are the same, just with different names? (Eliminates any chance of the file content causing a problem) Does the blank…
-
No. That is a function you'd put in the directory software, not JIRA. Internally, JIRA uses a cut-down version of Crowd and there's no desire to implement a full-on user management piece internally. If you need functions like that, it expects you to swap to a directory that can do it. Crowd has some functions in the server…
-
I think you may be asking for an installation demo. That's not something complex enough to warrant bothering making, as following the installation guide should be enough (our intern was able to do it without much knowledge of computers beyond "I've used Word")
-
JIRA and Tempo don't have any code that would cause that to happen on a regular basis. What else is happening at 12pm? What do your logs say? Check the audit log in the UI, and the application logs in JIRA-home/logs
-
No, you can't do that, and I don't think you ever will be able to - the delegated permissions are creeping into the permission schemes, so you'd need to keep them locked to prevent a project admin granting themselves all admin rights.
-
Without the macro definition, I can't really get a grip on this at all. However, there is another thing to try - delete the user macro completely (as you've blanked it out, it's not doing anything anyway). Re-index Confluence, and restart it. You should then get pages with "unknown macro" on them, but it should have…
-
I apologise for not being able to write this in German, but my education failed me on languages (other than English and Latin) This is usually because you are behind a proxy, but have not quite got the Tomcat connector settings correct. Go to <install>/conf and look at server.xml - check that you have proxyName, proxyPort…
-
Ok, can you describe exactly what "can not edit" and "cannot change plugins" really means. Do the options appear? Errors when you try to change things?
-
I'm afraid the link does not open.
-
If you are using a proxy and SSL and Confluence 6, then there's a pile of knows problems with it even when you get all the config "right". Well worth jumping to a later version instead of trying to fix it.
-
Yes, but you've tried the first thing that usually fixes it. We will need to see more of the log around the error, and probably the macro definition as well.
-
The stock answer for this from JIRA 3.6 until JIRA 7.2 is that a project admin can administrate * Users and groups in project roles * Components * Versions * Bits of JIRA Agile/Software 7.3 granted project admins some control over workflows. 7.4 allows more, including some field and screen stuff. As long as the config is…
-
It's an all-or-nothing thing. To see an issue on a board, the user has to be able to see the whole issue.