Comments
-
They are not. Application links are held in the database.
-
I'm afraid you can't. Dashboards are mostly based on filters, and filters find issues, not people. This means there's no way to filter for "person has nothing assigned" - you can find issues where the assignee is not a specific person, but you can't search for "nothing assigned to a user".
-
Confluence generally is not run with other applications in Tomcat - in theory, it can, but the standard installers won't set up Tomcat with anything that enables it, you have to do quite a bit of work to get it to work (ok, unless you're on a very old, unsupported version of Confluence based on the WAR/EAR distribution) So…
-
If the Kanban sub-filter is empty, then how are you marking things as "done" so they drop off the board? That could answer why they are missing.
-
Yes, there is a disconnect between Jira and Jira Software. Jira uses the resolution (which is something I think most people would agree should have changed from version 2 onwards), but Jira Software boards look at the right-hand column on the board, and ignore resolution. There's no such thing as "done done" in either…
-
Ok, this is one that definitely needs to go to Atlassian support - they should be contactable at https://support.atlassian.com/contact
-
Thanks @Davin Studer - I was concentrating on the admin/system stuff and completely left out "full content history is part of the system"
-
Might also depend on the board config: If it's a Kanban board, then "done" issues will not show. This depends on the "sub filter" for the board (as a board admin, see the bottom of the general configuration page). The default filter looks at the fix version - if one is set, the issue drops off the board, whatever the…
-
Yes, that would explain it. His Atlassian account is disabled, pending verification. It's probably part of an unverified domain (although there are some other reasons Atlassian do verification checks)
-
I am afraid this has too little context or information to be able to help you. What would adding this parameter do to the report? Why would it be useful? What is the actual question here?
-
No, you need a licence for each server, and unless you have "Enterprise licencing" (aimed at tens of thousands of users with many disparate services), they have to be per user of that server. If you set up a Jira Core on server 1 and Jira Service Desk on server 2, and you want 500 users to be able to access each of them,…
-
There is no way to change the way this behaves. The behaviour of the resolution field and status information is hard-coded throughout Jira. You must consider them to be in lock-step. Set a resolution on the way into an "ended" status (Closed, cancelled, done, etc, the ones usually coloured green and meaning "no further…
-
You should always ensure your resolution is matched with your workflow, so this is actually quite a bad idea. If you do this, you will end up with issues that say things like "open" and "done" at the same time, which is nonsense and confusing for users. If you insist on doing this though, it is not too hard. Write a…
-
Yes, Community is a good way to test an Atlassian account - if they can log in here (no need to post, just log in), we know the account works and the problem is with the Cloud site specifically.
-
Sort of. It's easier to explain it backwards. An issue can be thought of as "something that needs some attention". Each issue is unique, and lives in a project. Service Desk sits on top of a project and adds functionality over the top of it. One of the functions is that of "requests" - these are really a wrapper around an…
-
I'm afraid you have misunderstood my comment, as well as the previous discussion. I'll simplify: Q: Can I write a REST API so remote systems can create and update Jira issues? A: Jira already has a REST API that can do that. I never said anything like you should not create your own, I was just pointing out that the…
-
I am not sure why you are so focussed on the index. The index is a copy of your database, organised in a totally different way - it is designed to enable Jira to find issues fast. It is a set of local files that enable searching to be massively faster than running hugely sub-optimal SQL on a remote database. The index is…
-
Ok, I think that's a variation on "user has been deleted from the underlying directory". To test this, the most simple thing to do is get them to try to log in here (or any other Atlassian site) and see what happens.
-
Atlassian don't provide test systems (it sort of defeats the purpose of SAAS), so you have two options: * Buy a separate Cloud system to use as Staging (don't try to use a Server install, they're too different) * Use a "developer" Cloud system for it (I strongly recommend this one). See…
-
Yes, I am serious - the original question was about writing a plugin to provide a REST API that can create and edit issues. Jira already has a REST API that does that. So "why re-invent the wheel" is a serious valid response. Bulk edits - different story, but not mentioned in the original.
-
That's consistent with a bug - have a look at https://jira.atlassian.com/browse/CONFSERVER-56094
-
You need to remember what sub-tasks and stories are. A story is an item that needs some attention. It is something that you tell your people you are committing to work on during a sprint. A sub-task is part of a story. It is not independent of the story, it is part of what you are committing to. It therefore cannot be in a…
-
Ok, with errors at that level, you will need to be looking at the application logs to see what the internal errors are.
-
This is a bit short, but a lot of it is an essay question, probably better answered by a search on Atlassian docs. Some of these brief answers are dead-ends, there's nothing more to say, but we can expand on most or all of these if you need. For server: 1.1. HOW CONFLUENCE DEALS WITH ACCESS CONTROL ? User/password, but you…
-
1, 2, and 3 - yes, you do an export and import directly. See https://confluence.atlassian.com/doc/migrating-confluence-between-servers-184150.html The XML process is operating system agnostic. The "impact" is that you must stop using the old system before the export and then use the new one after import 4…
-
You are going to need to explain all of these problems. We can't see your system, and even if we could, you'll need to explain what you think is wrong with each item. For example - "Epics are not visible" is not enough information. What Epic? Why do you think it should be on the board? What is the board filter?
-
You'll need to explain where the work-around is failing for you?
-
We don't know, you have not told us what the warnings are.
-
That's one of the reports the App provides. The headings are all explained at http://www.midori-global.com/products/better-content-archiving-for-confluence/documentation/
-
You probably need to ask this in a Jitbit or Power BI forum