Comments
-
What validators do you have on the workflow transition that is failing?
-
Exactly what I'm trying to write a plugin for at the moment. As Neil says, we can do it with SQL, but it's not fast or flexible enough for my users, they want to click on stuff in Jira and get an answer
-
Very simple answer to this one - You can't. Whatever has destroyed your issue history has lost that data. This begs the question of what you've done to destroy the issue history and why, but that's not really part of the answer to your question.
-
Ok, that's a handler that behaves as I described. It won't try to do any field type processing. You need to find or write a handler that will look for and process your fields. Every time email is part of a question, the answer is pretty much "JEMH" - https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui If…
-
No, I'm sorry, I was not clear. What mail handler are you trying/using/looking-at in Jira? The mail server doesn't matter as long as Jira can read/write it.
-
You have not said what email handler you are using. The default handlers are quite simple - they populate summary from subject, description from the body, and they make some assumptions about reporter, assignee and issue type. That's it, they don't do any more. Your field mappings need something more advanced, so we need…
-
The resolution field automatically takes a value when it is used on screen. Open up your edit and have a look - even when you have no value set on the issue, the resolution will have a value, you can't blank it, and it will be set when you commit your edit. You need to remove it from the edit screen entirely.
-
No.There's a username and password for a local admin when I'm using existing data. But a clean empty one gives me just a licence box when I select "I have a licence"
-
A text box in which to paste a licence.
-
It shouldn't do - I just get a licence box
-
This question comes up a lot when people have JIRA installations that are not on the internet - the installers try to go to your my.atlassian account to create/fetch a licence, and when they fail, they stop. It's not always obvious that you need to go do that step manually on an internet connected machine (go to the…
-
1 will work if the groups and users are in the same directory 2 will work, but not for duplicates, and you can't put the users into groups in the other directory
-
Ok, how are you trying to get the second AD group to be auto-filled? What makes you think you can do that?
-
I'm sorry, I'm a bit lost now. Are you trying to work with duplicated users/groups or not?
-
Yes, I saw that it's one AD with two "links", but the problem remains the duplicate entries Confluence sees two directories with duplicates. It does not "fail over", because it sees the users as different entries, even when they have the same login.
-
Hmm. >when I shifted it above the existing working directory profile in priority everybody logged in with an AD account lost all permissions I think that's the problem. Let's say I'm nbrough, in group badger in AD1, password mushroom. You have nbrough in AD2 as well, but no badger, and password snake. I can log in when AD1…
-
Because original estimate is a specific type of field in its own right, which in turn suggests that the add-on can't handle that one type.
-
Nope, that screenshot is fine. I think the add-on is broken, as what you're showing us should work. Except for one obscure thought - do you have a custom field called "Original Estimate"? If you do, could you rename it?
-
Could you show us the selection of fields on the validator config? And a full list of all the validators you've got on the transition.
-
You have added a broken validator that isn't checking it correctly then.
-
Yet again, you're completely missing the point. The vast majority of the answers are not selling, they're offering ways to help people achieve things (or sometimes, telling them that they simply can't). When add-ons are mentioned, it's rarely sales text, it's because they're a good way to achieve a goal. Splitting it in…
-
I'd vote up what Natalie just said if I could. You're railing against the wrong people, in the wrong place and asking them to stop trying to help give good solid solutions to real issues people have. There's nothing right in what you're doing.
-
A huge budget? For free add-ons? Really?
-
Please don't have a go at people for making suggestions for "use an add on" when there is nothing built into the product. If you read the answer and comment properly, there's no sales pitches here, it is purely "it can't do it natively, have a look at some add-on options". Also, note that the JIRA Suite utilities are free.…
-
The answers given above on this question answer that - right place, but you need addons
-
Ah, yes, I think the one in the JSU only does custom fields. I've seen one that does system fields, ubt I can't remember where, sorry!
-
Fair, we only got you half an answer :-)
-
Workflow validators. Look for one that says "field(s) mandatory". There's one in the Jira Suite Utilities, but there are other plugins that provide them as well.
-
Unfortunately not. The only real fix I know of is to "not send duff email" - when I saw it, it was mail from someone using emojis on a 'phone, we just had to get them to stop.
-
Check the logs. I suspect they'll contain hundreds of rows of "error processing email" which are down to invalid characters being in the subject or body. I think the errors will contain "Incorrect string value:"