Comments
-
Search for the issues, then look at the tools option at the top right of the result. Note that you need to have "bulk edit" permission as well as the right to set security on the issues you select. As an admin, check what group(s) have that in Admin -> Global permission.
-
Exactly what my memory is muttering at me (I really do need to clean all these java versions off this machine...)
-
I did something similar a while ago with a very hacky install. Could you confirm the versions of * JIRA * Java * Scriptrunner
-
Go to the project and find the file the error message refers to. When running the build, you need to make the build script run against that file. (The easiest method is to simply "cd <location of file> and run the build there)
-
Have a look at the error message. It tells you that there's no build file to work with. You're running it in the wrong place, or you've renamed/deleted the file.
-
Ah, that makes more sense. Your support call response contains a load of stuff that is completely wrong for version 3.12 - the directories are wrong, the contents of osgi stuff etc. Next thing to look at is your server move. It sounds like you created a new empty Standalone Jira and then imported your data. That's good,…
-
There's something significantly wrong with your installation if you are missing the contents of osgi plugins, bundled plugins and the index directory. Could you give us a bit more detail on your setup - start with the current version of Jira - have you upgraded from 3.12 to a later version? If not, then those missing…
-
I'm not sure it's 7.2.2 that has bugs. These errors strongly suggest that you have an add-on that is not working properly. Could you * Check that all your add-ons are valid for this version * give us a little bit more of the log - the warnings/errors before your snippet might tell us a lot more.
-
Umm, it should be a 7.something?
-
What version of JIRA Software did you go to?
-
No, the component field has a lot of advanced code structured around it. However, which part do you mean? The basic handling of components is the same as a multi-select-list, so you could start with one of those.
-
I'm afraid you'll need to tweak some code to do that. The 15 minutes is a pretty arbitrary minimum, but a sane one for a large installation, to keep the load down
-
Check that they have the "set reporter" permission in the project, and to get them on the assignee list, check for "can be assigned issues" It's likely that you can't add the reporter field because it's already there.
-
There's several things this could be, but the most common culprit is that the database connection has been severed for some reason. What happens if you stop and restart the service? Can you check that the database server is accessible from the Confluence server? Check ip address and by DNS name. If a restart doesn't help,…
-
1) You can't. Get your users to shorten their list of status. In the issue navigator, that only lists status that are valid for the currently selected project. 2) Yes, that's for Atlassian. I've worked on other workflow engines though, and the ones that don't have a skeleton are an absolute nightmare to rename, edit,…
-
Think of the steps as a skeleton to hang the rest of the workflow on. Also, forget them, from the users point of view, they don't really see them, they see Status. That's a (Translatable) label you can apply to show the user what step they are on. I know it would seem more intuitive to throw "step" away and just say…
-
No, and you've found out why there is a 1000 limit by default - the process is heavy on the system and slow. Rambanam has a very good point - why does someone thing a 23k export is needed? It's no good saying "because they do", the question is what are they trying to achieve? There's almost certainly a much better, faster,…
-
Oh, sorry, yes, in the standard docs, http://confluence.atlassian.com/display/JIRA041/Database+Schema . It's not complete, but that's good enough for most, because it changes often enough not to be worth being complete, and frankly, if you think you need a full definition, you're probably trying to do something WAY too…
-
Nevertheless, that's the problem - it sounds like someone has removed the issue security scheme in the database, and I really do mean "it's better not to mess with the database". You mention "closing" the issues by using database access - you do understand that you have to amend doezens fo tables, while the database is…
-
It's better not to mess with the database. The security field on the issues is telling you that there is an issue level security scheme in place, and it's that which is preventing you seeing them. You just need to amend the security scheme, open it up to allow your users more access. See…
-
Subtasks don't appear in the planning view because they don't need to. Because they belong to parent issues, they don't need to be prioritised. Apologies for the next sentence, it's not easy to explain in words: It's not logical to have a subtask from issue A that is a higher priority than one from issue B if issue B has a…
-
The usual culprit is lack of resources - JIRA has become very heavy on the load at startup, especially with one or more of the "big" addons enabled. See https://confluence.atlassian.com/display/JIRAKB/JIRA+System+Plugin+Timeout+While+Waiting+for+Plugins+to+Enable as a starter.
-
We can't see your support calls, and the server locked message usually tells you what the problem is anyway. Read the log file for full details on what has gone wrong as soon as you can, that's quicker than waiting for support to ask you to read it for them and then have them tell you what it means.
-
That's not really what Service Desk was designed for. Customers are supposed to be simple individual customers. Raising things on behalf of customers is an Agent function. You can arrange your customers into organisations and share requests across organisations (I think that's only in Cloud and JSD 3.3), but there's no…
-
Do NOT try it in the database unless you know exactly what you are doing. To help convince you of that, can you name the 18 tables you need to check and potentially remove data from? Personally, I use REST for huge updates. It's slow, it's clunky, but it does mean I can leave a script running gradually deleting issues from…
-
You can add dates, but they won't have any functionality other than being a date field.
-
I repeat - custom fields are for issues. There is no way to add fields to versions.
-
No, custom fields are for issues. There's no way to add fields to versions. I'm not aware of any plugins that do it well enough to be usable either.
-
There is no bug here, it's your config somewhere. Three basic things: 1. The field will only appear for a user who has "can assign issue" permission in that project 2. If a user matches the "can be assigned issue" permission, then they are displayed on that list. 3. Is the "assignee" field on the screen? Simple test - when…
-
Ok, check the bottom of the log again - there may be more errors there.Also, look for the file "catalina.out" - that should also be telling you more about why it's throwing that particular error (but check the atlassian-confluence.log first)