Comments
-
They're just being deselected from the board (a board is a view, not a container), the issues are all still there. Just not shown. You can use the search to find them, or browse the project.
-
It's not immediate because of cases like yours, where people make mistakes. You can't delete accounts that own things because that would destroy the record of who owns something, which would be painful for people, and illegal.
-
Last time I paid attention, it was simply alphabetic.
-
You can't immediately delete an Atlassian account (and you can't delete them at all if they have any associated data like licences etc) You'll need to log into the old account and change the email on it.
-
With Kanban, your process is supposed to include a "release" step where you take everything in the "done" column and say "we've released these"., which clears them out of the column. You should find a release button at the top of the column. Use it regularly, and your done column will look a lot better!
-
Your app can be coded to talk to Jira over its REST API. See https://developer.atlassian.com/cloud/jira/service-desk/rest/
-
The move issue screens are not configurable. This is because, moving issues should not happen often, so the screens don't get used much. If you're regularly moving issues, your process is a bit broken.
-
You can't do this in 5.8, it does not track the changes in a way you can extract. You'd need to be comparing backups of the system line by line
-
Where? Could you explain what the user directory is? (e.g. Atlassian account, Jira internal, LDAP, etc)
-
You should avoid deleting Jira issues, it's a nightmare trying to recover deleted items, and if you allow delete, someone will use it incorrectly and dump your admins with that nightmare. If you really just mean you don't want to see an issue in the done column, then, often, you can adjust the config of the board to…
-
The colour is to give users an at-a-glance view of the issues. Blue = we've not looked at it, yellow = we're working on it, green = done. Grey = not selected one yet.
-
Yes, it does not care about the directory, just that the user is in a group.
-
Yes, you are right - the next-gen templates do miss sub-tasks, completely. If you want them, you'll need to create "old" style projects.
-
Because I am trying to help. I've had a lot of help from people in this community and I like to put something back. Is it better that we leave someone flailing and vastly misunderstanding how it works, and not grasping that it is not going to work the way they might think it is, or would it be better to engage, ask and…
-
>The problem with sub-tasks is that you can't include sub-tasks in a Sprint independently. That's not a problem, it's correct. A sub-task is part of the story you are telling people you are going to complete during the sprint. You do not commit to doing part of a story in a sprint, it's either going to be done or it is…
-
I'm not an Atlassian representative, and if you read the comments properly, you'll see that I'm not advocating this particular approach for them either. Where I'm telling people they are wrong, it's about how it currently works, not how it should. Personally, I don't actually care too strongly. I understand some people…
-
What type of project are you creating? The standard create project dialogue will ask you for a type. If you're not using that, then it's an individual project, which won't have subtasks.
-
It's because Atlassian accounts are used to access many Atlassian things, many of which are owned by different people. We're both using one now to talk here. It's the same as other identity providers - google, facebook and steam accounts are other examples - the accounts belong to the user and allow access to different…
-
I am sorry, I was not clear. The reality is the account belongs to the user - your opinion of who it belongs to does not match this reality.
-
Ok, that looks like it might be an individual project, which doesn't have them.
-
System admin can perform all the admin actions. There is a system admin group (or groups) that say who is a system admin. Only system admins can add people to those groups if you're using the internal accounts. Jira admin can only configure the application stuff (modify schemes, fields, workflows, users etc). There is a…
-
Because the pages have not been amended since creation? Although, it's well known that Atlassian databases are a terrible thing to look at in terms of reporting, and you probably should be looking at some other way of doing what you're doing. What is the reason you are looking?
-
Is this an "individual project" or one of the standard types?
-
Click "add issue type" to the left, and select one or more of the available sub-task types.
-
No, your opinion does not fit with the reality of it here. You do NOT own the account. You've invited it into your system. @Betty Quaywrote up a decent approach to fixing it in between my comments, although it suffers the weakness that the user can start seeing different names in different systems, which is…
-
Go to https://www.atlassian.com/software/jira/download and click on the drop-down next to the default selection, there's a "zip archive" on the list
-
That suggests the proxy server is not able to reach those pages. We can't tell you about the config of your servers, we're just end-users as well. I think you need to talk to your admins.
-
Upgrades are covered at https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html
-
The "work description" is part of the work log, not an issue field. You have to enter a work log in order to enter the description of the work.
-
I suspect your old Confluence had one of the add-ons that enables tabs - navitabs or composition for example.