Comments
-
You said are the project administrator. That's not enough, you need to be the JIRA admin to bypass security.
-
Your user has to be a JIRA administrator to be able to bypass the security.
-
JIRA doesn't support nested groups on Cloud, there are no workarounds at the moment, the software simply doesn't do it.
-
I have no answer for you, but I do have a question - User macros are not enabled for users on Cloud, so I'm curious as to how you got one there?
-
Yes, changing the username to lowercase in "user management" is the best way to do it. JIRA doesn't use the user name directly, so you need not worry. SQL is unquestionably the wrong approach, as you would have to be 100% certain you've not missed anything. That's why I said changing the username to lowercase in "user…
-
Yes, that is what a burndown is for. It's also trying to show you projections on how you are doing, and when the sprint ends, it can tell you how accurate your estimates were. If you go changing estimates or logging time outside a sprint, then by definition, it can't show you any of those numbers.
-
1. You don't. Projects have a single key 2. The automation and reporting is designed to inform your customers when things change already. You can set up notification schemes for the JIRA users though. 3. Yes, you can remove fields from the JIRA create/edit screens and only put them on transition screens. 4. We use it…
-
Yes, that's what I said - create an account for them, with the access it needs.
-
Sounds like my-host-ip is not set up correctly
-
Correct. You should be able to search for all the old issues and use "bulk edit" to set the level on them.
-
I already answered that. If there was a solution, I'd have mentioned it.
-
No, that's the point, it makes the burndown and other reporting work correctly - they tell you what you estimated and what you did.
-
I'd hook up Confluence to JIRA's user directory - see https://confluence.atlassian.com/doc/connecting-to-crowd-or-jira-for-user-management-229838465.html
-
I can't answer "best" - that's subjective and depends entirely on what you need from your reporting. For an opinion, I'd say Tempo is a very popular, powerful and friendly timesheet system for JIRA, but I'm quite fond of Andriy's Timesheet reports if your focus is just on reporting. Have a read through the results from…
-
Thomas is right, there is nothing like this. Notification schemes are for issues, not configuration. You'll need to write add-ons that can hook into it (I've not seen one to do it) The only tracking there is currently is the audit log.
-
>since we have many schemes which cannot be done manually All schemes can be done "manually". I don't understand what you mean here.
-
And the other things you might have damaged?
-
>Do you create a seperate task for the 2 days, >Or do you up the estimate? Neither. The original estimate stands as "how long we thought it would take". The time logs show "how long it actually took". Changing the original estimate is the wrong thing to do because we need to know what the estimate was, and logging…
-
Yes, changing the username to lowercase in "user management" is the best way to do it. I am not sure it will fix your problem, although my instincts say it will.
-
Look for "key" in the list of fields you can add
-
Indeed, JIRA Service Desk does it the other way around. You have the option to "create knowledgebase article from this JSD request", which creates a Confluence page linked back to the source request. JSD also has the search option. As the customer or agent starts to enter the request, it will start to suggest articles. The…
-
Ah, no, I'm afraid not. The Service Desk works by layering a portal over a project. So requests created in a portal are backed by issues in the project the portal belongs to. In theory, with a bit of code, you could move the issue, but this would drop the request from where the user created it and move it to another place…
-
No, because boards do not belong to projects. Use the "create from project" option when creating a new board, and then mould the new board to suit the team using it.
-
It might be. It depends on what your permission scheme says. It is common to have a permission scheme that says "Project Administration rights: Project Lead and People or Groups in the role of Project Admin", so you should check that (and, of course, that your in a group named in that rule)
-
There's a drop-down to select the sprint in the chart.
-
No, those three release categories are fixed. You'd need to hack core code to change them.
-
Right, the Portfolio add-on. Do you have project administration rights on all three projects you wish to include, and do they all support versions?
-
Go to custom fields and rename the custom one. Stick a . on the end or something. You'll then be able to tell them apart.
-
There is no one way to use boards, projects and issues, it depends on your processes and users. JIRA Software was built with the Agile methodologies in mind, so you have Kanban boards and Scrum boards. A Scrum-master will tend to want to use a Scrum board because it does sprints, backlog, planning and velocity stuff, all…
-
Problem - that could be being generated by an add-on or internal function. Could you please just tell us the url?