Comments
-
No. Not because it's a bad idea (it's a really good idea in real life), but because Atlassian Cloud is supposed to be a "managed service", where the end-user, in theory, does not need to see the server logs at all. In the "cloud service" model, you should not need to see the back-end logs, so you don't have any access to…
-
What are you using to define the "subtask's progress bar"?
-
I think this needs more explanation - what is RBAC, and what are you really trying to achieve here?
-
Service Desk is the only real way to get "free" customer accounts. I've seen a number of attempts to run help desk style systems in Jira without SD, and a lot of them work very well, but only when the customers have full Jira licences, and hence full access to the issues they are raising. By far the best option in your…
-
Joins are for joining tables together, Jira does not do this because it is not table driven. What you describe does not need SQL0like joins, it only needs logical operators. Adding "and label =" is the right thing to do, but you've forgotten to add the clause that selects for "and epic's label is".
-
You've not read what I said about them being clumsy when you have large numbers of options (which is generally a bad idea anyway)
-
I agree with @Bill Bailey about the instructions and process for the more recent versions (it's been pretty straightforward since 5.1-ish added a load of wizardy things) I have tried Confluence (and Jira) on Pi, using "Dietpi" for really minimal installs - I'd forget it on a 1 or 2, but a Pi 3 can bring up Confluence 6 and…
-
Our milkshake brings all the developers to the yard. Just that one sentence, as the summary and description, with absolutely no other data. Person who raised it did not respond to the questions. We still have no idea,
-
As long as Jira can read/write the database, yes, it will work fine.
-
No. Every issue needs a unique ID otherwise you can't identify it. Jira has a simple "use next free number in the project" scheme to generate these numbers.
-
The pie chart tries to display all the data you give it. If you want to drop some labels from the display, you have to exclude them from the data, by making the filter behind the pie chart ignore them.
-
Have you tried the Jira chart macros? https://confluence.atlassian.com/doc/chart-macro-163415075.html
-
Yep, I'm running my home confluence on a "minimal" linux distribution - there's no gui, and not even most of the other things you get from a standard install. Confluence, ssh and a backup tool are about the only things on it.
-
Start at https://www.atlassian.com/software/jira/guides/getting-started/basics
-
No, it means the calculations in the plan are made based on the issue data. If they're inaccurate, then it's because you are putting bad data into the issues.
-
Changing the project's lead does not change the assignee of issues, so I am a bit confused by the question. But I'll take a shot. An issue does not need to have an assignee, unless you have turned off "allow unassigned issues" in the global configuration. To change the settings for a default (not required, just default)…
-
As there is no "numbering of the backlog items" in Jira, I am a bit lost as to what your question is here. Could you explain what you are seeing and why you don't want it in more detail?
-
To "retrieve" them, click on them and Confluence will provide a download of the file. For backing up, follow the standard Atlassian recommendations for backing up Confluence.
-
No, Trello is a lightweight issue tracker, not a place to write docs
-
The Atlassian instructions work perfectly for me, and config.sh is where they say it is. Could you explain why you have installed Confluence and moved the config.sh file?
-
What do you mean by "mask"? If you mean "hide it", why don't you just edit it out?
-
This is either a network problem with reaching the page, or you have a broken plugin. The server's log (<jira or confluence home>/logs/atlassian-<application>.log) will tell you what the problem with the plugin is.
-
Yes, follow the standard upgrade docs you've found.
-
You need to remove the resolution from the create issue screen. As you have it configured now, your Jira is broadly useless as an issue tracker, unless you are only using it as an "already fixed" issue system.
-
Yes, this is correct, you're using bulk edit to change the parent. If you just want to change the issue type of a sub-task, filter for only sub-task types and select to move the issue type only. When I try this on the Jira I'm looking at, only the issue type changes - I can't see a way to make the parent change without…
-
I can't tell you how to match your Jira to your processes because I don't know what your processes might be. All I can really tell you is that you are trying to do the right thing - make Jira match your desired process. On a couple of points though: >where the Business Analyst / PO can click a button once the issue is…
-
You'll need to export and save them. I can't tell you how to do that, because I don't know what you actually want to save.
-
What does the log file tell you the problem is?
-
If you have Jira Software, you can create a board and tell it to include the issues from the business project, but you can't replace the business project board with it.e
-
One of your administrators has added some "clever" code to a field that exists for this project. You will need to get an admin to remove it, as it's broken.