Comments
-
1. There's not that much point in talking to anyone - the prices are at https://www.atlassian.com/software/confluence/pricing?tab=self-hosted (You will need to choose between Server and Cloud, but the prices are there) 2. Yes. You can make spaces and then pages within them visible to "anonymous", meaning people who have…
-
As Priyanka says, go through the docs first. When you have worked out where the problem is, then make sure all Jira processes have been shut down before you remove the lock file.
-
I can't read that log. What does it say the problem is?
-
Yes, I already explained that above. 90 values in a select list does not have a problem, other than being a bit of a pain for users to find the right one.
-
Security levels block access to people who do not match the rules. The most simple security level scheme you could set up would be a single "level", which names you (or one of your roles or groups). If you do not fill in a level on the issue, then everyone who can see the project can see the issue. If you do set that level…
-
Service Desk is an application for Jira. Go to Admin -> Manage Applications to install it. The setup of your urls is best done with a proxy server.
-
The licence is per-server. You will need to get a new licence for the new Cloud server, for your 4-5 new agents.
-
Most of us use proxies to do this. A proxy can take the existing installations pretty much as you already have them (ok, you have to edit the server.xml to tell the Tomcat it is behind a proxy) and serve them up on different urls. You can use the same ports on different installs, and have the proxy drop the ports…
-
Go to "manage applications" and look at the number of users it says you have for each Application.
-
Ok, this still means you are not using the right type of field though. The AIERule field needs to be a select list for your reporting, not a text field.
-
Yep. Set a security level! See https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117.html
-
There is no heirarchy. Let's say you've set up a scheme that sends to all three of those sets of people. If a person is one of those three, they get included in the email. If they are in 2 or 3 of those sets, they get included, but Jira de-duplicates so they don't get 2 or 3 emails.
-
That suggests you have anonymous access enabled. Check who has "browse" in the project permissions
-
You don't really. Boards draw in issues from projects, they don't work with schemes directly. Have a look at the board configuration and check the filter the board is using to select the issues it displays. The filter needs to include all the issues you want to see - it sounds like at the moment it's doing something like…
-
Ok, that's better, I think you've run into https://confluence.atlassian.com/jirakb/creating-issues-in-jira-7-throws-error-multiple-entries-with-same-key-815570970.html
-
You can't. I just said that.
-
Not really, the paid tools are the ones that have the money in order to pay for proper development and testing.
-
My guess is that you have resolved the issues (any value in the resolution field tells Jira that an issue is closed).
-
Very much so, yes. You can have the same, partial overlapping or no status in common between two workflows and represent both on the same board. You can then put status from each workflow into the same or different columns.
-
Yes, and the concept is still nonsense. A sprint is a set of stories that you commit to dealing with in the sprint. A story is either done, or not done. If it's not done at the end of the sprint, then it moves to the next one. Sub-tasks are part of a story. They're "in a sprint" because they are part of the story. It's…
-
You look at the filter. The filter you have there will list issues in project XY as long as they are of type story or sub-task. If it is not returning any, you don't have any of that type in that project. I usually prefer to use "issuetype in subTaskIssueTypes()", to catch all sub-task types though.
-
A burn down chart shows you how you are doing against what you committed to at the start of the sprint. It burns down when a Story is marked as "done" - that's what you committed to and you achieved it. Either a story is done, or it is not, therefore estimates on sub-tasks are useless in burn-down. If any sub-task is…
-
I'd recommend using any resolutions that describe why you have closed an issue. They're there to fit your purposes, and the language you use. The default ones, fixed, won't fix, etc are not a bad starting point (I usually add "duplicate" quite quickly though), but the real answer should be driven by your reporting needs.…
-
Absolutely. In the case you describe, I would use assignee as intended, and have a user picker for "approver". I would probably think about setting a script to re-assign the issue to the approver when they need to take action, and then on to someone else when they approve
-
Again, the view restrictions cascade down.
-
The Atlassian SDK is not a .Net application. I'd try installing using the instructions at https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-windows-system/
-
I described a simple set of restrictions done at the top layer. It works further down as well. So you can do * Home (unrestricted)* Business strategy (view restricted to only internal users) * Operations (view restricted to only internal users) * Docs for application X * Internal (view restricted to only internal users) *…
-
That's exactly what would be utter nonsense to your users. Having more than one name for a field does not work for them, or on the back end.
-
You can't do this in Service Desk - a request is either available or it is not. You can separate the requests out by group by using "organisations", but this will not allow you to restrict the request types to an organisation. For that, you'll need 9 separate portals.
-
There's no way to do this, and it does not make a lot of sense either. Field names should be consistent, not state dependent, or you'll just confuse your users. Also, imagine any you have two issues, one in one status so that "assignee" comes out as "assignee", and one in another so you want "approver" - this is nonsense…