Comments
-
What do you mean by "split"? What are you trying to achieve?
-
I've seen it work on global transitions, that should not be the problem. Check the logs from when it should be sending and how you've configured the transition.
-
What does the marketplace entry say for Cloud?
-
The "latest" result will happen whenever you run the query. If, for example, you use Daniel's curl example, you will get the current issues that match the query.
-
To expand on this slightly - there is no function for this in JIRA - you determine who can see issues on a *project* level, not issue type. Tim's suggestion is to us the "security levels" function, which hides individual issues based on the value in a field. To tie that to an issue type, and do it automatically, you use a…
-
Probably vast. Depends on what you mean by "JIRA Incident Management". Service Desk is an application which adds a load of service-desk functions to JIRA. I've no idea what you're referring to with the other one (a set of addons, local config, etc?)
-
Sounds like you did not have Jira shut down when you ran your SQL. Check the value of the sequence_number_item again - I suspect the cache has overwritten your change. Did you re-index after restarting as well?
-
Again, Llook at the table sequence_value_item There is a line in there saying "worklog" Make sure it is set higher than the highest ID in the worklog table The number is irrelevant - if you added lines to worklog with IDs of 10010, 10011, 10012, 20001, then make sure you set the worklog counter to 20002 or more.
-
Oh, I see, you weren't increasing the counter. That's one of the problems with direct access - people miss a lot of the application/business logic and don't make all the updates they need to. Look at the table sequence_value_item. I think you probably need to increase the counter named "worklog" so that it is at least…
-
Ok. Do not write to a Jira database while it is running. You will break it. To answer the actual question though, yes, you can jump numbers as much as you want. Jira will simply re-read the starting counter after you start it and pick up where it left off. It doesn't care about missing numbers or how big the gaps are. The…
-
Check the access to the Software application, and that it is installed properly under "manage applications"
-
There's only one screenshot and it doesn't show the field.If you are able to close the issue, then either you HAVE set a value for the field, or you have made it optional. I am not sure I can put it any other way
-
If you've set it mandatory, then you have to place a value in it. You can't get to "issue can be closed without it", the field has to be there to create the issue, edit won't let you commit without it, and you won't be able to complete any transitions without it either. What you have described you have can't happen. So you…
-
Google says https://confluence.atlassian.com/support/support-response-slas-277250944.html
-
I think you want to start at https://confluence.atlassian.com/servicedeskserver031/setting-up-slas-802164805.html
-
There's several things that could cause this, have a look at https://confluence.atlassian.com/jirakb/troubleshooting-jira-startup-failed-error-394464512.html to get started on debugging it!
-
The application logs under <JIRA home>/log and the Tomcat server logs in <JIRA install>/logs
-
What do the log files say is going wrong overnight?
-
Absolutely not. If you're finding problems that make you restart it, then there's something wrong with your setup.
-
JIRA itself doesn't, because it's an application that runs within an application-server and relies on that for networking stuff. Does the application server you are using accept TLS calls? (probably Tomcat? Definitely Tomcat if you've just used a standard JIRA install)
-
This is not a permissions error - your installation of JIRA seems to be damaged. The first thing I would try based on this error is disabling the Agile add-on. The error refers to problems with "greenhopper" which is the old name for Agile that's hung around in the code. The other thing to look at is the workflow - do you…
-
Ah, I think you've run into a bug in Jira. The default issue type scheme is supposed to have all the issue types in it, but sometimes, something goes wrong and they go missing. The issue type is still there, but because it's not in the default scheme, some stuff goes wrong (such as issue move!) I seem to remember you can…
-
AH! Got it! https://confluence.atlassian.com/display/JIRAKB/Unable+to+Move+Issue+to+Another+Issue+Type+Due+to+'The+issue+type+selected+is+invalid'+Error
-
Ok, I still don't know what the problem is, I'm a bit stuck and probably do need to look at the logs However, one long-shot idea. Could you go to the "issue type schemes" and look for your target issue type. Can you check that it is in the *default* issue type scheme AND the issue type scheme you have in the target project?
-
Ahh, I see. Thank you for explaining further, I know it's annoying to have to keep trying to explain to people who are not understanding a problem. I apologise for not understanding. I'm a little stuck on this because I cannot tie that Russian error message to anything specific in Jira. Is that the whole error message you…
-
Ah, good point. If there is nothing shown in the drop-down for issue type, then the project only uses either 1) Only the same issue type you already have 2) No sub-task types (and your issue is a sub-task type).
-
Ah, that would make sense. I'm going to blame lack of coffee and a hard week at work for not being awake enough to think of that.
-
That's correct then. I'm struggling to see the problem here, sorry.
-
Ok, I'm not sure there's any error here. You can't move to an issue type that does not exist in the target project, so it's telling you that you need to select one.
-
Mmm, I don't speak Russian, and I'm never sure Google Translate will give us a full meaning that explains what Jira is trying to tell you - "Selected type of request is invalid" is a bit vague. Does it mean your issue type does not exist in the target project? Could you compare the two projects to see how they are…