Comments
-
This thread is four years old. But still valid - changing tempmax won't help if your JIRA has been locked to prevent you overloading it by increasing tempmax.
-
1000 is a number judged low enough to avoid the performance problems a large export causes. If you need it changed, you'll need to talk to your Studio provider. They're unlikely to increase it because of those problems. A far better question might be to ask why you're exporting 1000s of issues - Most of the time, it…
-
It will, yes, but there's one other thing - if someone has used "anyone" in the permission scheme, then that opens it up to, well, anyone. Can you check the permission schemes for that?
-
I'd say that the users with unwanted access are simply in groups that have been unnecessarily added to permission schemes and/or roles that they should not be in.
-
Yes, you'll need to go through all the projects and revise their schemes and roles to ensure the right people can do the right things. One of the reasons for sticking to groups going into roles is that you can re-use a standard permission scheme for most or all projects.
-
Ah, ok, that's good, no hacks. The next thing is to work through the groups with the "create" permission then.
-
So, let me get this straight. If you remove ALL the groups from a role that allows "browse", then your users can still see the project? If that's true, you've got a hacked JIRA - someone has removed the permission setups.
-
Once you've got the groups removed from the permission schemes, you should find it is a bit easier. Have a look at the permission scheme line that says "browse". Hopefully, it should now say something simple like "Role developer + Role User". Now go to the project roles and look for any group (and user) in either of those…
-
Yes, that's correct, if your admins are demanding to do things that way, they're wrong, and you can't do what you need to. Frankly, they need to stop being silly and stop using groups in permission schemes. It's not the only solution to your problem, but it is the best, and none of the others are going to work until they…
-
Look closely at the "create" permission in the scheme for the projects. The users are getting the projects in the drop down for all projects that they could create issues in. Generally, you want to avoid using groups in schemes, your description seems to be that you're granting permissions twice and that's a bit of…
-
There is no field type that does that, although it might be worth a look in the marketplace for something that can add it.
-
I'm sorry, the question appears to be asking how you change from a date picker to the same thing. Could you explain it differently?
-
Project type is just a template, it doesn't have any effect after you create the project. However, what you do need to do is make sure the target project is compatible with the data in the source - check all the schemes in use are compatible and all the custom fields are the same.
-
Also a good answer, I focussed on the "field" part of the question. A third option too, which is a bit less precise than a field or a link - put the url in a comment or text field. It'll be a link in there as well.
-
As an admin, you can add a url field to the list of custom fields.
-
That's because "hiding issue by status" is not really supported, or even supportable. So, yes, I'd expect this behaviour. Searches work off the index, which deals with permissions and security scheme, but does NOT index workflow properties (because they aren't generally of any use in a search, and if you start mucking with…
-
That's your email client pulling up people from its saved addresses. Try cleaning out your contacts, removing anyone in the address book with that incoming email address.
-
Oops, sorry Peter, crossed over with your answer.
-
It won't be resolved. You need to move to a supported browser (remember that you shouldn't be using IE8 according to Microsoft, let alone Atlassian)
-
Looks like your index is broken. Try running a full re-index, after checking that the directory you've told it to use is fully read/write for the user that you are running Jira as.
-
The vendor needs to be set up to accept it. If you're aiming to pay for Atlassian licences via paypal, they don't offer it on their website. Contact sales-at-atlassian-do-com by email to see if they have another option you can use.
-
It's trying to avoid losing the edits made by both users. Merging what they are doing is the best option at present. Last year, Atlassian demonstrated a basic dynamic collaboration on a page, so that you can see other people actively editing it, but we don't have a firm timeline for when that will be available.
-
No, they're independent status objects, you'll need to add one of them to the workflow, move all the transitions from the one you want rid of, then remove the old one.
-
That looks like a Scrum board, so no, there's no migration to be done on that.
-
Correct, it's completely the wrong place.
-
That's true - the doc is fine for telling you how to change a key, but doesn't make it clear that there's a "hang over" of some data.
-
I'm afraid Ravi's answer here is not correct. Any project keys you create are recorded and kept for historical reasons. JIRA will prevent you from creating a project with an existing key, that makes perfect sense, as you already have a project with that key. But it will still prevent you from using a key that existed…
-
Yup, that's it - when you named the transitions you added the (2). Possibly because they were duplicate names and JIRA did it for you.You should be able to simply edit and rename each one now that you don't have the original transitions
-
No, the "all" should cover it. But if you had transitions with the same name when you created the "all" for each status, that could have caused it.
-
I can't remember if it's automatic when you reuse an existing transition name, so it might not be a totally human action.However, the other possibility is an addon doing odd things to the names. Could you nip into the workflow and click on the transitions to see what their actual names are? In fact, it would be easier…