Comments
-
The sub-tasks are created in a "to do" status, so they go into the "to do" column. Note that the parent issue does not have any separator columns, it's just there as a container for the sub-tasks.
-
If you don't have "create" in the bar, it usually means you do not have the permission to create any issues in any project. Have a chat with your admins.
-
At the top of your screenshot, there's "you are viewing an active workflow". Click "edit draft" to make changes to the workflow.
-
Um, the "clone and move" add-on?
-
No, not "anyone under browse project". Group (anyone) under browse project.
-
Yes, with Issue Security. See https://confluence.atlassian.com/adminjiraserver071/configuring-issue-level-security-802592414.html
-
Confluence is not intended to work that way, so you'll need add-ons. Try "Forms for Confluence" and "Confiforms"
-
They expect you to use "create related issue in development project". The idea remains that the SD issue is for talking to the customer and tracking the request, and if work needs to be done by developers, it should be created separately so the dev team can manage it in a development process.
-
That is not currently the plan, from what I heard on Team Tour. It will be a DC-only feature (but I suspect it will remain as a dark feature in Server)
-
In the project permission scheme(s), use the line "Browse project: Group (anyone)" Never ever give anonymous users write access, as you won't know who they are if they do edit anything, and if, for some reason, you ignore that, do not expose this system to the internet, as you will be found and spammed quite quickly. Also…
-
Point c is the one that stands out to me. Either you always need to enter a port, or you never need to. If you need to enter it some of the time, that tells me the network is not routing port 80 (or 443?) irregularly which will break your gadgets, pictures and feeds exactly as you describe.
-
Very near future - they've already switched it off for several blocks of Cloud users, expect it to happen for everyone within weeks at most.
-
As I said, check the permissions on the project
-
Sorry, the three dot button on the far right
-
Click on tools on the issue. If you have the permission to delete, then the option will be in that menu. If not, then you'll need to amend the permissions to grant it to yourself. Be warned, this forum is full of people asking how to undo a delete - the answer is "slowly, painfully and expensively", so I usually recommend…
-
There's no way to do this. You can do it all-or-nothing - if you remove the searcher for a custom field, no-one can search, but you can't do it by group or user.
-
That is a "clone and move new" action, not a "move issue". As such, it's * not an answer to the original question * not a move, clone does not clone the subtasks, only the parent
-
There is a grey tick to the left of every answer. Click that to mark it answered. Atlassian are active here, but they don't often take conversations here as requests, and when they do, they raise them in JaC as suggestions. You can do that as well - go to https://support.atlassian.com/contact to be routed to the right…
-
Permissions. Check what the permission scheme says for "assignable user", it probably says "Role: Developers". If it is a role, go to the project admin and put your group into that role (and maybe remove anyone else who is in there)
-
Using the same email address for another user is a really bad idea, it causes problems if you are using the internal directory for access, and if you have mail handlers processing incoming mail. That said, if you have fully deleted a user, there is no problem re-using it. So, as you seem to be asking, I assume you are…
-
Generally there is no need to unlock these fields (it usually goes horribly wrong when someone does it), so I'd question why you want to do it. But, to answer the question, you can't do it on Cloud.
-
Field defaults only apply on create issue. You don't want them to occur on transition or edit because people will set fields to the default when they wanted to leave them blank. I think what you actually mean is that when you click on an empty date field in transition or edit, the picker starts at "today" because that's…
-
Repeating the question with no new information on what has gone wrong tells us nothing. Yes, I can import.
-
DC does support shared storage for some parts of the installation, as it needs to. But you should not try to use shared storage for Server (or try to cluster it or anything like that)
-
Ok, that's clear, thanks, but I did read your scenarios, and I was very clear on what to do. In that case, do not estimate on sub-tasks. The simple fix if your users ignore you is to remove the "time tracking" field from sub-tasks completely.
-
Although, even if you restrict them, they can still give themselves access. Igor uses the word "impossible". It is the right word here. If you need to hide things from your Confluence System admins, you need to do it by storing the data in another system that they don't have access to.
-
First, decide if you are doing this with Agile Scrum or not. If you are, then stop estimating on sub-tasks, that's not what they are for If you are not, then it's fine to estimate on sub-tasks, as long as you remember that they are for breaking up issues, not estimates.
-
Please, have a think about the real world * The age of a request is utterly irrelevant compared to how useful something might be. Different things. Why should I implement something 10 people have wanted for 10 years when I could implement something 100,000 people have wanted for a week? It's far more useful to spend time…
-
Stop estimating on sub-tasks and do it on stories. Have another read through this discussion, the points questions and clarifications remain valid now.
-
Let's step back. I can think of nearly 16 ways to import issues before reaching for code, so I think we need to narrow that down to what you are looking at. In other words, yes, I need to know the step-by-step. Not actually most of it, but let's say the starting steps - how do you get from "I log in to Jira as an admin and…