Comments
-
There's something wrong with the create issue process, it's not indexing correctly. Could you check what validators and post-functions you have on "create issue"? List them all here.
-
Ok, I need to simplify this down to a basic test. Create a new issue in XYZ. Go to somewhere else in JIRA outside the current project (dashboard is fine). Type the new issue ID into the quick search - do you get taken to the issue? Next test, go back to your "project = XYZ" search - does it appear in the list there?
-
You may have a broken index, but could you tell us what "advanced search" you are using to start on the debugging? Just the plain text of the JQL please
-
I'm not sure what your code is doing, but yes, you can have a workflow start in any status you want. I think of the "create" process as a transition that doesn't have a start status, but does have an ending status. I've not tried the workflow designer in anger, but in the old workflow editors, you could open up the "open"…
-
How are you implementing the "clock"?
-
You'll need to do some more detailed debugging to find out why - when does it happen, what is the error message and so-on. Most importantly, you might want to find someone for whom it does not crash and check how your IE is set up differently from theirs (Cloud is working fine on my brief test on IE11 off-the-shelf, so…
-
I'd just point to your other question(s) in a link and mark one of the answers here as correct.
-
I think you're going to need to give us an actual question here...
-
Yes, check the permission scheme in the project. You'll find there's a line that allows you to delete. Grant someone you trust that permission and they'll be able to delete from the project. Things to bear in mind 1. You might want to allow them "bulk edit" global permission too if there's lots of them 2. Jira deletes are…
-
You'll need to explain that in more detail - 2 LB and keepalived are not Atlassian functions
-
Oops, sorry Ram, started my reply before yours arrived!
-
You can't - Jira diesn't do field level security. https://jira.atlassian.com/browse/jra-1330 The two standard workarounds are the Quisapps field security plugin, or moving the field off the "edit" screen and into "transitions" only, so you can control who can get to edit it.
-
Actually, with fetchmail and the local folder option - Jira does support "email from local file", so you wouldn't need all the cron/REST stuff. Getting the mails as files, I've done for another system which wasn't really email, so I'm a bit stuck on that bit, but it's not too hard to implement the "read files, create…
-
Ah, bad admin ;-) (For not talking anyway) You can't add rules - the code is quite simple - it says "on edit, fire event X", "on log work, fire Y" etc. That's it for the system events - certain actions are fixed to fire certain events. Only the workflow lets you fire different events for actions. I seem to remember that…
-
Enable higher logging of the email classes in logging and profiling - that should tell you what it's doing.
-
And, as a reminder, because it's your own question and you seem to be asking exactly the same again: This flag is only for test systems, and becomes unreliable with prolonged uptime and usage.
-
Generally, you can, because the format of the exported xml is not that different between versions. Go to the list of workflows in 4.2 and look for the xml export option. Use it, and take the file it creates, and import it in 6.x See https://confluence.atlassian.com/display/JIRA/Sharing+your+workflow for some of this, but…
-
What happens when you go into the list of status (in the admin screens) and look at the status that isn't appearing? Is it JUST the issue view where it doesn't appear? What about the navigator?
-
Ugh, definitely a bug of some sort then. Does the status come out if you search for issues and have an issue-navigator view that includes it? Can you actually search for the issue by status? Can the issue be moved through the workflow (does it at least offer you the option)? By the way, in your example, you said "Bug" was…
-
It's not a real url for their system - he's changed it to avoid leaking information.
-
That's an interesting problem - is it all status showing that, or just one? Is there no icon there at all? Could you examine the plan html of the page to see if there's anything there at all?
-
Generally, trying to transition an issue while another transition is still executing does not work. What you've got there would probably work fine in a listener, but I've never seen it work in a post-function (in fact, had jobs cleaning up the mess made by people trying to do this) I do know it can be done - the script…
-
This is a known issue - Agile does not let you drag between status in the same column. Yet There are several similar issues raised with Atlassian, the one I stumbled on first is https://jira.atlassian.com/browse/GHS-9720
-
Ok. If it is already a sub-task, then that rules out weirdness in the time-tracking "roll up" (where you estimate say 1week on a parent issue, do no work on it directly, but work on the sub-tasks so that the parent ends up showing several days work)
-
Yup, that looks wrong to me. 2 weeks estimate - 1 week logged = 1 week remaining to me. More questions though I'm afraid: Does this issue have any sub tasks? Can you look at the issue history and look for any changes to the timetracking? And similarly, examine all the worklogs? (I've found when I've had time-tracking…
-
At a guess, look at your timetracking settings. How many hours per day and how many days per week are set? Secondly, you say "2 weeks from <date>" - the start date is irrelevant to time-tracking, all that matters is the estimate and the logged work. As your estimate is 2 weeks, and your developer has logged one day, I…
-
You close these by marking one or more answers as correct. I'd recommend your "user error" one :-)
-
Which example code? Although, that error usually means your network has failed for some reason - pulling a network cable, proxy server not letting you in, packet loss etc.
-
Which example code? Although, that error usually means your network has failed for some reason - pulling a network cable, proxy server not letting you in, packet loss etc.
-
Boris and I aren't Atlassian, we're end users like yourself (although both of us work for Expert Partners) There's also no way to gather metrics on what end-users of Server may have hacked into their systems.