Comments
-
It is. Go into Jira admin and find the application management. In there, you can add groups to the "this group can use Jira Software" permission. Check out "global permissions" as well.
-
Could you look through the log back to where the indexing errors occurred?
-
I think you need to explain this "agility" board, as there simply isn't one in any of the Cloud or Server systems I have access to it. Pleas,e give us a screenshot, as I doubt we'll get anywhere using different language.
-
There is no single firm recommendation on this. You can put more than one Atlassian application on a server. As long as that server has the resources to run each of them. The only risk of doing it is that a single server is a single point of failure, and if something goes wrong, it can affect all of the services. In my…
-
What is the problem with linking? Jira's web links don't really let you describe the relationship, they're just a pointer, but there's a couple of add-ons in the marketplace that extend the data for links.
-
Yes, and remember to read the log to see what it is doing.
-
Please explain how this solves the problem?
-
Could you explain how it solves the problem?
-
No, because a search returns issues. If there are none, there's nothing to search for. The best you can do is repeat the stuff above to get a list of projects that do have issues, then subtract that from the complete list in Admin -> Projects.
-
That's a symptom of a broken index. As you've said you have already tried re-indexing, I would suggest that there's something wrong with the indexing. What do your logs say 1) When you visit the dashboard 2) When you try a full re-index (not background or project, do everything) Also, can you search for anything and get a…
-
Depends on the application(s) being installed. But not many. Before 7, you used to just get jira-users. Jira 7 has three applications now and gives you a group for each as well as jira-users - jira-software-users, jira-core-users and jira-servicedesk-users depending on which ones you install and how. The rest are the same…
-
Fields like due date go on to issues, not the board. The board is a view of the issues, and the due date can hence be shown on the cards that represent the issues on boards. Releases use the "fix version" field. With Kanban, issues are supposed to move from left to right, gradually filling up the far right hand column as…
-
No. Jira uses the assignee field to mean "This is the one single person currently responsible for the issue". I'm told one of the reasons it was written was because of the problems caused by allowing multiple assignees - it is inevitable that there will be cases of "I thought someone else named was doing it". However, the…
-
It's understandable when you're frustrated by something and it's not giving you enough to explain what's wrong. The screen in your image is the "link" dialogue for creating a new link, it's not for attachment maintenance. Cancel that, save your work, and then use the "attachments" option in the ... actions menu near the…
-
I always enjoyed "Kings and Things" - https://boardgamegeek.com/boardgame/58/kings-things
-
Heh, I'm going to an escape room tomorrow! One variation I enjoyed was "The Room" - less an escape, more "work out how to open a puzzle box", but very well done (mobile devices only I think). Fireproof games
-
Yes, "download" will take you to the public downloads. It is just a download, you'll need to run it or unpack it on a server (or your local machine) Your licence will work for any version from 4.0 to anything released before the end of your licence!
-
I don't think it's this, but is the user part of the rule for the new level? Can they change the security level to the desired one by editing the issue in the UI? Are you making other changes to the issue in the script? If so, are they working?
-
Sorry, I missed the download bit - yes, you will need to download a new Jira and install it, same way you created production.
-
Go to your "my.atlassian" account and find your production licence. Underneath it, there's a link for "development licence" which will give you a different key to paste into your dev system.
-
Core "business" boards don't have the colouring facility.
-
All the time. You apply it in exactly the same way as any other licence and you get the same user numbers and end-date in your test system.
-
Run a search for the issues you want to report on (e.g. "created > startOfWeek()" ), and save it with a sensible name. Now go to your dashboard and add a "filter statistic" gadget, selecting your saved filter, and "status" as the field to look at, and I suspect you should check the "show resolved issues" option too. You…
-
Timeouts like that are either * Internet speed (just because one site loads does not mean your route to another is any good) * Network blocking * Browser or software blocks on your machine * Server not delivering content fast enough The last one could be down to problems with code, a page that's simply too large or the…
-
Localhost means "this computer". Give them the address of the server, not their own computer.
-
Looks like the css and other resources have not loaded. Check your network is not blocking things, refresh tthe page, and have a look at the browser's "dev tools" to see what isn't loading and why
-
Could you describe "do not see our dashboard"? Blank screen? Menu, but nothing in the body? Empty gadgets? Anything wrong with the gadget titles? etc?
-
Because tasks are not sub-tasks, and don't have a parent, so they can be ranked against their peers. The peer group for sub-tasks is "the sub-tasks on this issue", the peer group for tasks is "all other tasks at my level in the backlog"
-
The atlassian docs on searching are quite "dry" in my opinion - they tell you everything, but do not tell a useful story in context. As an example, the query you've written does work, and (hopefully) tells you what you what you were looking for. But if you had a story about how it was being used, you probably would have…
-
Cloud systems are updated and changed frequently and when these are happening functionality is limited. Give it an hour, then try again. If you get the same message then (or if you've already waited a bit), raise it with Atlassian Cloud Support