Nic Brough -Adaptavist- Expert

On server, yes, it is safe, but I never delete, I move the files to backup directories outside the installation just in case. On Data Center, no, it is not safe, unless you do the same on all the nodes, which does mean making sure the whole cluster is down while you clear the files out.

I assume by "submitted efforts", you mean the work logged on issues? If so, check the permission scheme on the project - there are rules in there for "who can edit a work-log", "who can work on issues". A lot of us do things like "Project admins can edit other people's work logs" + "you can edit your own work logs" The…

Some of the loss of function may restrict access to your data, or make it unusable, but the change won't physically lose you anything. The licencing only impacts what functionality you can use, not content.

What is stopping you creating an issue type scheme with a sub-task?

I suspect another admin has accidentally made one or more fields mandatory for the request type. Check what the request form says, and what is mandatory in the issue type behind the request.

You will always lose "what the parent was", because issues don't have a parent, but all the other fields will be kept (even if they're not on screen), as long as they have "context" for both issue types. If for example, you set up a field called "wavelength" that only exists on "technical tasks", and another called…

Welcome to the Community! Filters do not contain fields. Filters are essentially a question asking Jira for a list of matching issues - "show me all the blue issues" or "give me a list of issues that have my name on them" The questions can of course be based on fields, but they do not contain the fields. Gadgets based on…

Odd. But the next thing to try is completely filling the parent column. For the parent issues, try a self-reference: Summary, issue id, parent id, issue type, epic link Client Implementation, 21100,21100,Epic, Confirm client data, 21101,21101,Task,21100 Confirm connectivity,21102,21101,Sub-Task,

Excellent! At least it was something readily fixable! Glad to be have been of some help in finding it!

I'm afraid that really does mean what it says - the connection you have configured for the database points to a database that it can't get into. Check the bitbucket config file (bitbucket.properties under <bitbucket home>/shared) contains the right host, user, password and so-on, and that the connection settings can be…

Hmm. How are you doing the create? Clicking in a column on the board or create in the menu bar, or something else? Do you have any automations active in the project (or global ones that might be looking at it), and have you checked the workflow for this issue type starts with Create -> To-do (or whatever, the important bit…

Yes, that's just one of many possible schemes for working with estimates on sub-tasks. There are plenty of others. But you still have to come back to the fact that sub-task estimates are not directly relevant to the sprint. Also, you ask "Why doesn't Jira allow you to move only a couple subtasks from a ticket forward into…

This means your build process does not have the certificates required to access that repository. You may need to install them manually. If the machine doing the build connects to https://packages.atlassian.com/maven-external/ does it get the same error?

Nope, no change, and it's not going to. Issue trackers are supposed to ask for, and present, the same information depending on their type, not who is asking.

I think you might have meant this to go to one of your organisations administrators or help people? It's nothing to do with Confluence, or any other Atlassian product, I suspect you've clicked on "help with confluence" instead of "help with VPN"

Ok, so what does the history say? Who moved it through the transition from "to do" to "done", and when?

Please don't say "resolution status" - it does not exist and the phrase is unhelpful as it could be being used to mean resolution OR status. For this issue type, try placing the resolution field on the "create" screen.

When you say "marked as done", do you mean it gets crossed out as "resolved", or do you mean "it gets created in the to-do status, but then transitions to a done status"? If it's the first of those, then check your create screens and post-functions, make sure the resolution is not on screen and not being set by a…

You don't get access to the database on Cloud. You'll need to do your reporting properly, with the Jira macros, or imported reporting. Or find apps that can do the reporting you need. (Not a bad thing, as reporting on a Jira database with SQL is the worst possible approach because the database is absolutely not built for…

Ok, so "Change resolution" is not appearing anywhere in that list? I'd expect it to be a bit below "change comment" - the first batch of fields you see are "system" fields, so it usually falls in there. The second section is an alphabetically sorted list of custom fields. The other thing we need to check is that the…

Where are you seeing this error, what is the system it is running on? (What's the server running, and who owns it - AWS, Azure, your own server or VM, that sort of thing?)

You need to stop jumping around between your two startup systems and second-guessing what all of these files might be. etc/init.d is one way of handling services, systemd is another. They work differently, but because you've got both active in your system, they need to be a little bit aligned. Forget the init files for…

Ah, I see, sorry, I mis-added up the numbers and didn't spot the "done" issues are being added to the in-progress count. As the numbers are being added to the in-progress column, that suggests the five issues are not sub-tasks, which is one reason they wouldn't add up. It only really leaves us with the possibility that the…

Cloud doesn't yet support the solutions given

A quick text description would be enough - for example Login -> Admin -> System -> External system import -> CSV is the one I usually think of when the word "import" is used.

Ok, that's good. When you get into the process though, where are you looking for the resolution field? (I mean in the list of fields it presents to you - near the top, or in the area where you'd expect fields with names starting R in the list)

Not directly. You can't hook up a Confluence Cloud system to your own directory. But you can hook up Atlassian Access to your directory, and then use that as the user directory for your Cloud systems (including Confluence) Crowd is a very different beastie to Access, but it is equivalent in what it does - if you were on…

You can see the accumulation of time for an issue and its sub-tasks with the sigma fields - where you see "original estimate", it has a sigma variant called "Σ original estimate" However, these only exist for the time estimate fields, and they do not apply to other numeric fields such as story points (as you do not…

That's the same. It really does look like the estimation statistic you've chosen for the board is not what you've got in the issues.

Ok, that's correct, but you need to do some mapping in the Jira import for issue type. It doesn't take the string as is, you still have to say "where you see Bug in my file, that means the issue type called Bug in Jira". That is, unless I'm not looking at the same import process you are doing. Can you run us through what…