Comments
-
It's only clauses that are going to be changed by what the user is entering, which instinctively feels like it's the wrong thing to be checking.
-
The screens have nothing to say about the options on fields, they are simple lists of fields to present to a user when something happens.
-
Mmm, it doesn't make sense to do that with JQL, why not check that the field is filled?
-
The mandatory flag on a field means it is always mandatory - you need to either default the value in the background or put the field on the create screen. I suspect though, that you don't want that. To make a field mandatory later in the workflow, use validators to check that it is set on transitions.
-
I'm afraid the labels field does not support wildcard searches.
-
JQL really does only run against the index, there's no way it can search for stuff that hasn't been committed to. The two options I can think of are "JQL result set, modified by working out what the data entry is", or to take a different approach to coding it. On the second one, I do not quite understand what your code is…
-
That can be done without labels actually. Try the "page index" macro to a page.
-
Yes, if you're careful with settings and versions. Later versions of Atlassian stuff comes with its own version of Java and ignores what's on your server, so you're ok if you're on a recent one. For older ones, your environment should usually contain a setting for "JAVA_HOME". That's probably what is in use. But, if you go…
-
I'm not sure I understand the question, but it sounds like you mean you want to give the users a list of pages that are most likely to help them? Or even an index of all pages. I would probably use a "content by label" macro to give them a list of pages that I had tagged for attention.
-
Ah, sorry, you're on Windows, constrained by its poor tool set. tail -f is a *nix command which says "list the last few lines in a file on-screen, and display new ones as they get written to it". I don't know if there is an equivalent on Windows. It's not critical, it's just useful to see "this click caused those 20 lines…
-
You'll need to take that up with your hosting provider or Atlassian. We're just end users. Atlassian are here, but they don't provide formal support here.
-
Boards are not part of a project (even when they're created alongside them, and only look at that project), so they don't inherit settings when you use templates. I'm afraid you will need to do the settings manually. There are some improvement requests logged for things like "shared default filters for new boards" and…
-
It shouldn't be trying to connect to anything to log you in. I'd expect that to be just a problem with config, something to fix after you get back in. What errors are you getting when you try to login in? Try running a terminal with a tail -f atlassian-confluence.log ticking over while you do the login in a browser.
-
Ah, you'll need to use an older version of Java - 6.0 only runs on Java 1.7, 8 causes it to fail.
-
The technical limit is so large you'll have made your system utterly unusable before you put a dent in it. To see how many you have, look at Admin -> Issues -> Custom fields. As a general rule, I don't start to worry until a system hits 100, but if it has more, I start to look for reasons. I've inherited a system with…
-
Duplicate https://community.atlassian.com/t5/JIRA-questions/For-input-string-quot-PT14400M-quot-Error-on-Scrum-Board/qaq-p/626349
-
Do you recognise that as any data that might be on an issue?
-
I'd look at the LDAP server logs next to see why it refused to let Confluence in. Although, do you have admin access via a non-LDAP account? If so, then try going to the directory list and click "test" in the directory that is failing - sometimes the returned error can tell you more without having to dig into logs.
-
I'm afraid if it's not starting then there are only two places you can look. 1. What's the output when you run start-jira.sh (or whatever the start script you are using is) 2. What is the full content of the catalina.out - it's not just errors in there, there will be more information.
-
You could be better off looking at a "condition" than a "validator". A condition hides and blocks a transition if the conditions are not met. You can easily place conditions like "user must be in role", "user must be in group" and/or "user must be Dave" on transitions. Validators happen after a user clicks on the…
-
Ok, you're in the wrong place. I'd suggest finding some sites that talk about apache clusters and jboss.
-
>if we reopen a resolved case the case still shows as resolved Your admin should place a post-function for "clear resolution" or "set resolution to <none>" on the re-open transition. The resolution field is intended to capture a resolution when you resolve an issue. Because JIRA relies heavily on the resolution, it doesn't…
-
Could you explain what this has to do with Confluence?
-
Scripted fields are display only, they don't gather or hold data. A select list that doesn't do anything isn't a lot of use. What are you trying to achieve?
-
I honestly don't know if this is going to change. The last time I spoke to an Atlassian technie about Atlassian accounts, there were no plans for an API for them, but that was a year ago.
-
Your catalina.out is a lot longer than the snippet you posted. However, you've not explained "won't start". Have you checked it is running? If it is, and "won't start" actually means "won't respond to the browser", then check <jira home>/logs for other logs.
-
I don't know what you mean by that.
-
I expect the problem is that an inexperienced administrator has placed the "resolution" field on the "edit" screen for the issue type. You'll need to get that removed to prevent any further issues being broken, then we can look at fixing the issues that have been broken. Resolution should only ever be placed on transition…
-
You need to read through more of the error in the catalina.out, there's not enough of it in your post to start to work out what might be wrong.
-
Yes, it will work fine, as long as the VM has enough resources and a local disk.