Comments
-
JIRA (in fact, most Java applications) will quite happily use whatever memory you choose to let it have. If use of too much memory is an issue, reduce the maximum allocation. Of course, there is a minimum amount it will need, depending on the kind of loads you put on it. For information on how much memory you might want,…
-
You hadn't mentioned that you were using the wrong settings. There's no way we could have known that.
-
Cloud is well past JIRA 6.4.7, so it's not going to work. You'll need TestComplete to provide a version of it that works over REST (and/or a Connect addon)
-
You can't install add-ons like that in Cloud. Even if you could, you wouldn't have it - RPC was deprecated a while ago and it does not work for more recent versions of JIRA. Whatever you're trying to do, it needs to use either the UI, REST or Connect addons (which use REST anyway)
-
The wastebin isn't more load than a "redundant" status really, but I prefer the status because you can instantly see which projects are creating lots of junk. For both methods, an admin filtering for "stuff to delete over 1 month old" and using their bulk-edit rights to delete is a bit of a chore, if you decide you do want…
-
There's other tricks. A good one is a "wastebin" project that you move the issues into instead of deleting. It's a bit of a fiddle for the users, so it encourages them not to raise junk issues. Another friendlier one is to a "redundent" status in your workflow with a "delete" transition going into it. On it's own, that…
-
Sort of. If you define "their issues" as "this person is the reporter", you can use "reporter" in the permission scheme. Same for "assignee". You could also define an "owner" custom field and use that. However, before @Joe Pitt gets here, I'd like to strongly recommend not allowing anyone to delete. Issues are, well,…
-
Ok, but you have not given us the results.
-
Ah, sorry, I misread that last one. Could you please run the filter I suggested, as I wrote it.
-
So the importer has imported nothing, or you can't see the imported issues, due to permissions (or issue security) in the project. You need to look into that before doing anything else.
-
"I tried it" tells us precisely nothing. Did you use the exact filter I suggested? What does it tell you?
-
Could you try running a filter for "all issues order by created desc" immediately after the import to see what has come in.
-
What happens when you run the filter I suggested after the import? Please, use the standard JIRA issue navigator to do this, don't mess around with other applications.
-
How do you know it's importing them as "tests"? Could it have done them as a different issue type? Try running a filter for "all issues order by created desc" immediately after the import to see what has come in.
-
Ah, this again. @Jonas Andersson - yes, you're spot on. There are several sites who are documenting their Wordpress hints, add-ons, tricks, suggestions and so-on using Confluence. A number of the more poorly designed sites don't bother to offer good routes to help, support or forums, so people looking for help end up…
-
I think you need to talk to the people providing your repository. This is not a Fisheye issue - you've got the key, you can't upload it to git.corp, so you need help from them.
-
Go to your atlassian account and make sure the evaluation license you create is for Jira 3. Jira 3 and 4 have different license styles and they are incompatible.
-
Yes.
-
Log in as someone with space-creation rights, and click "create space" on the spaces menu
-
I've seen it done a couple of times. You can write VBS that can issue a REST call to Jira and pull back the results.
-
Whatever version you installed on it! Yes, you can upgrade it whenever you want, just check the versions supported by Stash before you do it.
-
Have you enabled and configured it?
-
No, all issues have to belong to a project. Because that's how they are keyed, configured, grouped and referred to.
-
No. Custom fields are maintained by system level administrators, there's no way to devolve that to project administrators. See https://jira.atlassian.com/browse/JRA-3156 for the progress on improving this.
-
And you actually answered your own question - the path you gave is where the file goes under the JIRA installation (on Server and Cloud, but as Volodymyr says, you don't get to hack the code in Cloud)
-
Right. That account is an Atlassian account, for using their bug tracker and other facilities. You are a user in there, it's not your system. You need to try/buy an OnDemand account. Start at https://my.atlassian.com/ondemand/signup/jira
-
You appear to be asking the same question again, rather than providing new information about where you are stuck. The question you are asking is covered in the documentation. Ramiro pointed you at the basic reading you need to do - start with the "Jira 101" stuff. When you've read that, to answer this specific question,…
-
You're mixing up "Field configuration" with "Field configuration scheme". And screens are irrelevant here (they are lists of fields to show a user at a certain point, they have nothing to say about optional/mandatory)A "Field configuration" is a list of fields, with their renderer, optional/mandatory, and visible/hidden…
-
You need to split the "field configuration" up - copy the one you are using in the project, set the problem fields as optional, and then change the "field configuration scheme" so that it uses the new scheme for the sub-tasks.
-
Go to "manage boards", find the one you don't want, and click "delete". You must be the owner of the board to do it. (JIRA admins can change ownership of boards if you need to do that)