Comments
-
Are you behind a firewall or proxy? This happens to me a lot when I'm not on a direct un-masked internet connection.
-
Jira does not do "field level security". You have several options though * Install the field security plugin from Quisapps * Write new custom field types that include restrictions like that * Remove fields from the "edit" screens, and place them only on "workflow transition" screens, then add transitions to your workflows…
-
This is a difficult one - on the surface, the first response really is "what does the log file say", but you've done exactly the right thing and looked already, and found nothing. My best guess is that although you don't think you have seen anything related, you have, but you've not recognised it as related. To rule out…
-
I've seen that done quite a lot actually. I've only got involved when it's been built with an Apache web-server front end, but it seems to work fine and I know you can do it with nginx and lightppd, so I'm 99.9% sure you can use IIS too. Anyway, you set up Apache to serve up your intranet as normal, but then proxy certain…
-
It depends on what you mean by "integrate". It does mean "work with", but that's about it, it's far too vague to tell us what you're looking for. Could you explain, in terms of what the end user might see in their browser, what you're looking for? One obvious tip though - most places I know either use Confluence as their…
-
That's the problem, JIRA simply doesn't have anything that would do that. There is code for checking password length and complexity in internal directories, but there's nothing that chops up passwords as they're entered, stored or checked. All I can think of is that there's something in the LDAP settings.
-
That doesn't sound right to me - I'm using at least one JIRA with openLDAP and a 24 character password that won't let me in unless the whole password is correct.
-
Your approach won't work. Even if you deactivate the user, it will still appear in Jira as deactivated, and it will hide the internal user. If you move the internal directory above the LDAP directory and then create the user in there, that one will hide the LDAP user.However, that leads me to another question - why? Why do…
-
The dashboard and space directory are configured globally - you can't turn them off for external people and have them enabled for internals (although removing "browse users" from external users will help a bit)
-
Write an add-on that reads and gathers them for the selected project and then puts them on screen. You'll need more than just jsp, as you'll need java at the back end to go read all the information. I'd point out that the JIRA project admin screen already tells you the current project schemes though. Also, I don't know…
-
It depends on how you want to handle it: If you don't want to code (or can't because you're on Cloud), then estimate at a story level. If you do want to code, you'll have to think through how you want the estimates to work and use something like the script-runner to implement a mass of fields and calculations to do it. For…
-
No, it's not built to estimate at that level (there are several ways to handle it, none optimal and none consistent ly used, so Atlassian have not yet coded for any of them)
-
My answer already answers those questions (But, no, it won't work and yes, you'll need to change something)
-
No. Last time I read about it, the plan was to drop SOAP in version 7 of Jira. It's there in 6, and there's nothing to stop you finding/writing your own plugin to provide a SOAP interface in Jira 7, but Atlassian won't be bundling it any more, or supporting it. This would be a good time to convert your plugin to REST.
-
Nope. Wrong. "My computer is broken" is not a title.
-
The problem remains that "title" is the wrong word for the field. It would be if JIRA were built as a documentation system, but it's not, it's an issue tracker (no matter that it has been used for all sorts of other things). I don't think "summary" is a great word for it, but I've yet to find a better one. Confluence is a…
-
Name or Title are dreadful ways to describe the field. Documents and people have titles. Items have names.Think of it like this - what is the field used for? If you put a sentence into the field to give people a rough idea they can use to think about the issue, how could you describe it?"My computer is broken" is not a…
-
What does that mean? You'd prefer Subject to Summary for the name of the field? It's not as good a word as "summary", because subject means "the person or object being discussed". But I might be discussing a principle, asking a question or requesting help. "Summary" works better for them.
-
You can't do it in the standard UI. Rambanam is probably suggesting that you use Javascript to create and populate it before the user commits a new issue.
-
Again, you don't really give a "name" to a bug. In English, a name is subtly different from a title or a summary. Names are generally proper and formal. You name people, pets, places and so-on. "London" is a name, it doesn't really have a title, and a "Summary" of "A large conurbation in England" is appropriate. My point…
-
Summary is a better word than title, it's a more generalised word than title. Title would be ok for some types of issue, but isn't really right for others in English. Bugs for example, wouldn't have a title, summary is a far better way to say it.
-
You are not doing anything wrong really. Summary is a mandatory system field, you can't create an issue without it. Jira is coded that way, and you can't make it go away. You have to fill it in. The best you can do is remove it from all screens and automatically populate it using a post-function or listener, but I've got a…
-
You can't add your own categories, it's an indicator of what applications you have created the projects for (the other option currently is "service desk") If you want to remove it, you need to hack the core code, as I said before. Look at the url you are on, it should end with .jspa - look for a file with that name but…
-
That's quite an important indicator, especially for administrators and you don't want to change it to anything else. You could hide it by hacking core code or using javascript to make it disappear. But you really don't want to.
-
It depends on which plugin you're looking at. Which one is showing the warning?
-
1. Actually, nothing until you run into a function it executes. Those happen in workflows and issue view, so you're probably ok 2. Possibly. If you're using JSU functions and they're incompatible, they could break. The JSU stuff is almost all workflow related, so if you don't move issues through the workflow, you shouldn't…
-
No, you have to be a JIRA or System admin to edit schemes. It's that way to prevent your project admins messing up other projects by altering shared schemes. There are some addons which implement some partial attempts at this delegation, but I'd look at this one…
-
To earn points, keep commenting and interacting, and ideally, getting upvotes. I don't like the look of that warning, it implies the system doesn't have complete read/write access to the data directories. But the "ready to serve" means there should be something there. Could you have a quick look at the end of the…
-
Ok, what is at the bottom of atlassian-confluence.log?
-
Sorry, didn't see the earlier comment. That means it is running. Or, at least, the Tomcat container is running. You should be able to visit the Confluence install in your browser now.