Comments
-
Well that's the problem, the field was not there, so it can't guess what you might want in it.As you suspect, you're going to need a bit of code to update it. A listener could catch the "issue moved" event and do the update for you there.
-
It sounds like you have not got the submitted date on the view screen for the new issue type, or it's hidden in the field config for that issue type, or it's not a valid field for that issue type (check context in the list of fields)
-
There is no wiki markup in version 4.x, it's been deliberately removed. See http://confluence.atlassian.com/display/DOC/Confluence+4.0+Editor+-+What%27s+Changed+for+Wiki+Markup+Users
-
I'm not sure you've read the answer I tried to give. I'll try it again, differently * Status is something you put in a workflow, one per step. * You can NOT use a status more than once in a workflow (because it's nonsense) * You CAN use the same status in many separate workflows * Status is drawn from a global list * If…
-
No, it's not telling you that. Your question seems a little muddled, and I'm not sure what is happening, so here's the three things that it *might* be. * Jira shares status across workflows. If you change the name of a status, you affect all the workflows that currently use that status * Jira will not let you have a…
-
Hmm. This isn't behvaing like a standard field. Could you give us a screenshot of it? (The whole issue screen, not just the area around the field)
-
Could this "work description" be coming from the work logs?
-
You could use either, but a post-function won't give a message back to the user and it's quite hard to make one actually stop the transition. You need to deliberately code something that will crash rather than just fail - things like trying to update non-existent fields will just fail and carry on, rather than blocking the…
-
There's no "retire" function. You'll be able to find some stuff about playing javascript tricks to remove it from certain screens, but there's plenty of ways around those tricks (using REST, changing the issue type later, or other create methods provided by addons) Your only real options are to rename it to something to…
-
"unzip atlassian-jira-5.1.8.war" works fine for me (Linux box). If unzip can't read your war, then there's something wrong with it.
-
Mmm, just because it's extracted automatically doesn't mean it's correct. You really do need to check that the war you are deploying is correct. What do you mean "not able to extract the war"?
-
Ok, that sounds healthier, so can you confirm the exact structure you've got under edit-webapp? To check it, could you take your built WAR file and expand it into a temporary directory and compare that tree with the file tree you get with an off-the-shelf war - basically we're looking to see that your modified files are…
-
Well, that's never going to work... > Copied the old /atlassian-jira directory to tomcats /edit-webapp eYou need to work through each and every change you've made to the base installation and place them under /edit-webapp in the appropriate directory. You can NOT just copy the whole of the atlassian-jira directory - you'll…
-
Difficult to say unless you can explain exactly how you built the WAR. Also, could you confirm that your old Jira and new Jira are totally separate installs on the application server? So there's no chance of the two mixing? (Reusing the same database is fine, it's just to ensure the new system is not going to pick up any…
-
It states you can use a *numeric* custom field for the estimation. Do you have any numeric custom fields defined?
-
You'll need some code to do this, and you need to think about when to run it (because if you store it and the data changes, you'll need to run it again to repopulate the target field) The code wouldn't be too hard - there's API calls for "run jql, with an order by" to give you a list of issues, of which you can then just…
-
The difficulty is that there wasn't enough information. We've all seen this sort of error before, but I don't have a huge range of similar incidents to work from, I've used less than 100 Jira installations. John has the advantage of a much broader swathe of incidents and can pick out patterns that I can't see. That's why I…
-
That's a front-end error again, although it does give us a bit more detail. You do need to be looking in the application logs though. Have a look at Admin -> System information. That should tell you where the logs are on the server.
-
No, I'm afraid there's no logs in your initial question. There is the error message the user sees on the front end but there should be something in your logs if there were a true internal error. However, if there is nothing in the log, then it's a strong possibility that your network connection is dropping or timing out…
-
I'm afraid there's not a lot we can tell you here. You'll need to start reading application logs, they should tell you what Jira and Agile think is going wrong. You should be able to find the logs by looking at your system information page. Of course, the errors may not be clear enough to determine the nature of the…
-
You'll need some code to do that. As usual, I'd reach for the script runner plugin and writing a post-function script...
-
Ok, Could you take a look at the "system information" page - is there anything listed in the section "modified files"?can you try disabling all the user installed plugins next - if it goes away, you can then re-enable them one by one until it reoccurs - that should identify the plugin to concentrate on (if it is a…
-
Hmm, ok, well, first, go over every field that should appear on that create screen and check if there is any javascript in the descriptions. If there is, remove it. Then retry.
-
What is the actual error?
-
It can't reach the smtp mail server - check your network has the right routes allowed and your connection settings.
-
>We automate the creation of JIRA issues, which adds all applicable Labels You could add the priority to your automation. If not, then you'll need a bit of code to be run as a post-function. I'd use the script-runner add-on to do it.
-
You'll need to ask EEA directly. We're just end-users, so we don't know (unless EEA see your post. You might want to get the EEA addon tag on it as well)
-
There's a few options, but the answer you probably want is simply Comala workflows
-
A transition can end on the same step/status it came from
-
Um, I don't work for them, I'm an Adaptavist. You need to contact them, and/or keep checking for yourself.