Comments
-
You can't upload addons into Cloud - see https://confluence.atlassian.com/display/Cloud/Restricted+Functions+in+Cloud+Applications That addon is not on the list of available addons either, so you can't install it on Cloud. The message about admin rights means what it says - you have admin rights at the moment, and you…
-
See https://confluence.atlassian.com/jiracloud/exporting-issues-737772285.html
-
Oops, sorry, I also meant to say have a look at https://www.atlassian.com/software/jira/agile/agile-comparison#!greenhopper-rally
-
Ah, ok, well, you probably want Jira + Agile, and the Portfolio addon may be worth a look to cover some of the PM level stuff Rally does.
-
Lots of things. This is a bit of a vague question, what are you really looking for?
-
Are you using external user management? If so, you probably need to check there. If not, then start with the Jira application logs - there should be an error in there.
-
Ah. I am terribly sorry That was not clear to me in the question, it was phrased in a very similar way and I completely misunderstood. I don't think we can reopen a question. That will work fine, with a couple of caveats: 1) The licences may fail. This is not a huge issue - your "developer" licence is valid for fail-over…
-
Duplicate of https://answers.atlassian.com/questions/134107/jira-fail-over-implementaion
-
You need to ask the person who signed up for the trial - they have the admin rights.
-
Adding users to a project is usually delegated to *project* administrators. Adding user accounts is done at a *system* administrator level. They are separate things To get one, or both, of these permissions, talk to your existing administrators - they'll need to add you to the right roles/permissions.
-
What comments? Are you trying to mark this question as answered? If so, look for a "mark as correct answer" next to Mathias or my answers (whichever one helped you more would be nice to do first)
-
Jira's SOAP and REST interfaces do not expose the "add item to custom field option list" functionality. If you do decide to start coding or digging into this, then bear in mind that only administrators can modify those lists as well, and you really don't want to be granting full admin rights to ordinary users.
-
It's part of the core functionality, and well documented at http://confluence.atlassian.com/display/JIRA/Associating+Issue+Types+with+Projects
-
Hmm. The error is straightforward - the SMTP server doesn't recognise the user id and password you're sending to it. This can be the error returned by "this user can log in, but doesn't actually have the permission to send" sometimes too. I think we'd like to see more of the SMTP error (should be in your logs, but if you…
-
My apologies, I was wrong. I keep looking at custom fields on complex Jiras and getting myself knotted up in them.
-
Nope. Wrong. I just tested it myself. A user granted access by "reporter" sees all issues. See https://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission
-
If you are on 6.4 then I suspect you are on Jira OnDemand. I do not believe you can enable "current reporter browse" there.
-
I am sorry, but this is completely incorrect. If you give the "reporter" the right to browse a project, then they will see ALL the issues in that project. Including ALL the ones someone else reported.
-
Can you divide your customers into separate projects? If not, then you can't do this off-the-shelf. Adding just "Browse: Reporter" to permissions will enable ALL users who can create an issue in the project to see ALL the issues in that project. If you can't split it up by project, then you need "Current reporter browse"…
-
Atlassian divided JIRA into three products. The development functions (including the source tabs) went into JIRA Software. It was announced when the split was announced, but there was a lot in there. I suspect Atlassian probably regard your usage pattern as very unusual and hence don't support to (source control on service…
-
That looks right to me.
-
If you are going to try this in the script console, then you will need to add code to the top of it to say which issue to work on.
-
Start with debugging what the fields are returning - your code assumes they are numbers, and that they are all filled in for every issue you are examining - are both of those actually true?
-
Yes, but don't. Especially with only 512Mb - I wouldn't try to run either of them with less than 512Mb. You're also unsupported - although it can be made to work (and I have done it, albeit with 3Gb RAM), if anything goes wrong, everyone will tell you to separate them before you move into any serious debugging.
-
Well, sort of. If you have less than 1000 issues in the project, you can export a good swathe of the data to csv and import it from that, or even more clever stuff. But if you want a complete project, you'll want to take a full xml backup and then use "project import" to pull that one project into the target JIRA
-
If you do a full export/import as recommended in the docs, it will bring all of that across. I'm not aware of a summary report which will tell you any of that in one go. You usually have to go into each one in turn and look.
-
No. Permissions are project level configuration. However, they do have some flexibility and you can do something like this. For example... If you use issue-level security, it's quite easy to set up post-functions to automatically set security (and beacuse you want to do it by issue type, you can have "set security level A"…
-
Depends on what you've configured. Are you running it behind a web-server? Have you set up Tomcat to do any? Have a look at the other files you found in the directory catalina.out was in - that's the most likely place.
-
Those are application logs, you need to look at access logs (you may not have any, it depends on the configuration of your application server and/or web-server if you are running one)
-
There's no way of knowing - it is someone with administrator rights, but the only way you might find out who is by going over the access logs looking for the "administrate subtasks" page being mentioned in there. Your best option will be to ask the other couple of administrators - as you should only have a small group that…