Comments
-
Admin does not mean "can do everything", it means "can do admin tasks" (admin can do everything is a dreadful approach and Atlassian don't do it). You need to add them to a role that has the assignable user permission, as Udo says.
-
You don't. Jira's permissions are permissive, not restrictive. To do this, you need to remove whatever it is that is giving your user access to the projects you don't want them to see, and then grant them the permission to see that one project. Take a look at how the "JIRA users" group is being used - you'll need to unpick…
-
Agreed - just don't get bogged down in the "jira-administrators" stuff - that is about *system* permissions. You need to check for *project* permissions. Start with the project permission scheme - it sounds like your permission scheme is missing "administrate project: Project Lead"
-
True, but we don't know that the poster is wanting a Mayan date. Or Hebrew, Hijri, Chinese, or or or
-
About three weeks ago. Is there a question?
-
Please, read the docs. It's in there.
-
Depends on the version and type of apache you're using. The docs for it will tell you.
-
Should be covered by http://httpd.apache.org/docs/2.4/mod/core.html
-
Scenario 1 is a mis-configuration in your apache server. You'll need to fix that. It's not a JIRA server setting, it's apache. And what Vasiliy said - you need to think about reverting to a supported version, or at least prepare to upgrade as soon as a supported higher version is available.
-
You're going to see a lot of https://confluence.atlassian.com/adminjiraserver072/upgrading-jira-applications-828787633.html But start with https://confluence.atlassian.com/jira064/upgrading-jira-using-a-rapid-upgrade-method-720411841.html to get you from 6.something to 6.4.latest
-
6.3 to 7.1 is the largest jump I'd make inside your area, and that can be painful. I'd strongly recommend an upgrade to 6.4.latest. This will minimise the issues you have going from 6.4 to 7.0, and I would test a 6.4 to 7.3 direct upgrade - it has worked for me recently (if you have problems, then fall back to 6.4 to 7.0…
-
Eh? OnDemand supports workflow schemes fine, and they give you "workflow per issue type" in a project. Have a look through http://confluence.atlassian.com/display/JIRA000/Activating+Workflow
-
Yup, we're getting there... 1) The mail is not stored, it's processed and discarded 2) Actually, that's another question, which you've asked over in at https://answers.atlassian.com/questions/60363/integrating-jira-4-2-1-and-jira-4-3-3 - it's probably worth continuing in that thread, as the title and history are more…
-
> pop server has to read that mails send to another jira-2 and issue should create and update at jira-2 Right, well that's helped me understand, although it still seems you have a fundamental misunderstanding as to what a POP server is. It really would have helped if you'd explained what you're trying to do from the…
-
1) What? Not even the section that says "Configuring Gmail for incoming mail (POP)"? 2/3) Your answers here have answered question 2 - you've got outgoing mail working. 4) I'm sorry, I'm still lost. Do you mean you are trying to get Jira to read a POP server and do something with what it finds? Again, could you explain…
-
I'm sorry if I seem terse, but you don't seem to be grasping what I'm saying. I may well be misunderstanding you as well, for which I apologise. Let me break it down into simple questions * The link I've given you states how to connect Jira to Gmail. I'm not going to copy and paste that here to provide you with the "STEPS"…
-
Um. That makes me worry - it sounds like you don't know what a POP mail server is. To connect Jira to one, so it reads the mail from a POP mail server, see the documentation I've referred you to - it's broadly valid for all versions of Jira from around 3.4 onwards from memory.
-
It's in the document. I don't understand what you're missing.
-
<sigh> You do know there's documentation to search? Like https://confluence.atlassian.com/display/JIRA/Using+Gmail+as+a+JIRA+Mail+Server
-
This is quite a complex requirement, so you'll need to do some coding or scripting. However, I'd have a look at the Service Desk add-on - that implements all sorts of tracking and, most importantly for your case, Service Level Agreements, which allow for emails and updates based on time without having to do any scripts. If…
-
You can not use system-admin on an OnDemand installation - it is limited to Atlassian support. That covers questions 1-3 For answer 4, you should only need to be a Jira Admin (which you should be) to edit the System Dashboard, from the Admin -> System Dashboard link (not by just editing it, you need to go via admin)
-
You need to give it a valid method - "attachments" is not a valid method. See https://docs.atlassian.com/jira/REST/latest/ for what is valid. You are close though. http://myhost/rest/api/2/issue/TEST-123 should return a load of metadata about the issue including a representation of a list of attachments.
-
There is no sensible way to do this. If a user can edit an issue, they can put any component on it that they want. The best you could do would be to add validators to the workflows that would prevent progress if the components were "wrong". You will probably find it easier to dump that idea completely and instead record…
-
Did you map your key to Jira's issue key? And is there definitely an issue with key PORT-3188?
-
Good, I wasn't 100% sure it would work on creation date, not tried it. You are correct about the burndown chart, it will burn down as you log work and resolve stuff.
-
1. See https://confluence.atlassian.com/display/JIRA/Importing+Data+from+CSVand look for "updating existing issues" - I'm not sure it will work for the created date though 2. Ok, so you have standard burndown charts as described. As long as you put the sprint data in.
-
1. You needed to set the creation date in the CSV, or it uses "now" because that is genuinely when the issue was created! You can log work in the past though, that's not an issue. 2. I'm not sure I understand this, but let's start with the obvious question - do you have Jira Agile installed?
-
You set the status of the issues to "open" in the import, but that is not a valid state in your workflow? Is that correct? You'll need to either do the import again with a valid status, or change your workflow to include "open", with transtions to where they should be, move them through to the right status and delete the…
-
It should not matter if you use user name or user ID if you tick the "map value" box on import. If you do NOT map the users, then you must use the exact user ID that they have have in Jira - their login, and exactly as it is in the user list - case sensitive etc. CSV can create components, versions and other fields.…
-
Are the users valid assignees for the project you are importing the data into?