Comments
-
Please could you explain all three of your questions in more detail, all you've really given us is out-of-context snippets of question. * What do you mean by "action item" and "remove"? (remove from where?) * Which text header? The body, menu, or something else? * I'd say drag the cursor over it, that highlights the text…
-
Log into your Jira as an admin, go to admin -> application links and create or fix the link to Confluence.
-
Ok, there's a couple of points here. * That document is for Server, not Cloud, as you said Cloud. * My answer was given in the context of Cloud, where you do not have a system admin rights, so the document is irrelevant for you. * Also, that document is written in quite an unclear way, it says the system admins have access…
-
Fix the second one first - the css problem not being read can be caused by the client not being able to fetch the css from the server, which can be a proxy problem. I most often see this when I've messed up the reverse-proxy settings in Apache.
-
You can't do this because it does not make sense. The point of the 2d statistics is that it shows you what issues have <field 1> and <field 2>. The number is there to tell you how many match each combination. Imagine you have 3 issues that match EDG and Desktop. These could easily be in three different status. So if you…
-
What went wrong? What errors did you get during upgrade, on-screen and in the logs? What did you do differently to the docs?
-
Note that you may still find some differences if you have used fields that are specific to issue types. The security level field does not apply to subtasks for example, or, more importantly, the context for a custom field might say "I am on Stories, but not sub-tasks"
-
Your administrators can add you to one of the groups that has the global "create space" permission (there may not be any, depends on the rules for your organisation), or they can create the space for you.
-
* Yes, you can use "issue level security" to set a "level" on an issue that says "only people matching a rule can see this issue" * Yes, you do that with the permission scheme * No, Jira does not have field security, but you can move fields into the workflow and control their editing that way (only allow people matching a…
-
I've not seen anything that would do that for the Atlassian suite. Could you explain why you are asking?
-
I am not sure what you mean by "Postman API". Postman usually refers to a tool that you can use to make REST calls to systems, not something that has an API itself. Jira Cloud has a REST API, and to get started with that, have a look at https://developer.atlassian.com/cloud/jira/platform/rest/v3
-
While you're getting "null errors", it is well worth ploughing through them - they usually chain together with a "caused by" which can eventually give you something useful. Without the errors, I'm afraid this could be almost anything.
-
Do you have the "resolution" field on the create issue screen?
-
There is no global "see all" permission, you would have to go through the space permissions for every space and make sure an account has "use" access, and then check the "restricted pages" for each space as well to see if they might be restricted there.
-
Yes, you can, but the nature of what you are trying to do is not provided by any off-the-shelf post-functions, hence the need for an automation or scripting app to provide it.
-
No, the upgrade assumes the database will not move. That's why I suggest moving database first - an upgrade is an intensive thing to do, and the internal database is not good at being loaded heavily!
-
Correct - if it's not selecting from A, it has nothing to do with that project.
-
The table is partly for ranking issues, but it only kicks in when you rearrange issues in a board, and before the balancing moves it back into the ranking field. I suspect you really want the lexorank table which holds absolute values, but is also not always 100% right, has values that will change even when a rank does…
-
They are two different actions. A project is an entire structure, filled with issues. Deleting a project has been flagged as a global administrator responsibility, no-one else's. Issues within projects are controlled by permissions, as you do have cases where someone might need the right, and most others do not. By…
-
Could you compare an issue that is correct with one that is missing? -3932 vs -3936 - status, resolution, issue type, summary are what we need to see (the structure, not exact content, obscure what you need to). Also what status are in the "done" column on the board?
-
First, you've completely missed the point of the conversation, and secondly, if you think something needs doing under GDPR, you need to consult with the people you agreed terms and conditions with when you signed up and they let you in to use their system. That is not directly Atlassian, as they host the system for someone…
-
Ok, that's the usual culprit for "burn down doesn't match story points". I think we need to identify an issue that should be included but is not. Could you look at the list in the issue navigator to see if there might be a pattern?
-
You will need to be an admin of your user account system (usually Atlassian site admin, but possibly Google or your organisations system that is using Atlassian access to give accounts to Jira). This will let you create groups and put people into them.
-
I would do it the other way around. * Set up an empty database. If you have no preference, the order we usually recommend is Postgres first, as that's what Atlassian use most, then MySQL, Oracle third and MS-SQL last. BUT, if you have any "looking after a type of database" expertise in your organisation, use the one they…
-
What do you mean by "resource name"? The urls you are using are part of the REST API, and are the thing I would describe as "resource names", and are documented in the docs you posted in the question!
-
I think you will need some code to do this. It might be possible in a user macro.
-
You can get Jira Server to show the sub-task header (including the +) with a minor tweak - just add a line in the properties file in the jira home directory and restart Jira. Mine usually reads as below: root@zen:/opt/home-jira# cat jira-config.properties jira.websudo.is.disabled = true…
-
Could you explain what i-tool is and what it has to do with Atlassian?
-
No, because it can vary. See https://confluence.atlassian.com/cloud/atlassian-cloud-ip-ranges-and-domains-744721662.html for the ranges of ip and names you need to allow.
-
Then you will need to restore Confluence from a backup taken before you damaged your database with SQL.