Comments
-
Unfortunately, no. There is a build number in it, but I don't know how to turn that into a version. Do you have any of the damaged system left? There's usually things in there that can help.
-
Is this Cloud or Server? If it is Server, then check the logs - look specifically for user directory errors
-
The installation process expects to be connected to an empty database, not one with data in it. Create a new empty database and run the installation against that. This gives you a working but empty Confluence. Make sure it's all working for you then stop it, go into the Confluence-home directory and edit the…
-
Customisation that can't be done with add-ons and direct database reporting (which is a stupid and horrible idea because the database is not in the slightest designed for it and is the single worst possible way to report on Jira and Confluence)
-
It sounds like you are just a Project Admin, not a Jira or System admin. Ask your admins to check your permissions.
-
Ah, not what I was expecting, but it answers it. Your board is set to look at Original Story Estimate. That's the column that appears on the right hand side adding up points. You need to put your estimates into that field instead of Story Points.
-
Ok, good, yes, it almost certainly is the workflow and backlog. You need to make sure the initial status in your workflow is in the backlog column in the board settings.
-
Yep. Last time I did that, it did take a couple of weeks before the spam started.
-
It is possible to set up a project with a permission scheme that says "create issue: anyone". The problem with doing this is that you won't know who they are, and that if you expose your Jira to the internet, you're going to get spam.
-
What does the workflow for the subtasks say? I suspect there are conditions on it.
-
Argh. please remove the quotes.
-
Hmm. I suspect you might be looking at the wrong thing then. Can you explain exactly where you are looking for the backlog and what type of board it is? Scrum, Kanban or Core?
-
Excellent! I'm a big fan of specific but reusable role names - user, developer or worker, admin, owner, viewer etc.
-
What does your board filter say?
-
Another test I need to do I'm afraid. Could you go to the board configuration and look at the estimation tab. I'd like to see what the list of options looks like on the drop-down (don't change it, just need to see a screenshot of the list after you click to get the list)
-
Indeed. I've wanted to take "field configurations" out the back and put it out of my misery for years, moving the functions to screens instead.
-
Most people really don't need it. I've run into several places that have implemented something to emulate it, and a lot of them have got themselves so knotted up in too many layers, they've lost all sight of what they're doing.
-
Structure can set something up that looks a bit like multiple layers. Portfolio can layer things above Epics
-
Only thing left is to move it to a different workflow (change the issue type, or move it to another project) and back again
-
Use roles. The trick here is understanding that you don't need 100s of them and you can mix and match. In your scenario, it sounds like you need at most 10 at the moment. I regularly work with vast Jira systems with hundreds of active projects, and tens of thousands of users, with 99.9% of the user management delegated to…
-
Yes, because you've got resolution visible in one screen, you see it. For B, you've removed it, so you don't see it. But, remember Jira does NOT set the resolution to unresolved, it leaves it empty, and displays unresolved (unless you've misconfigured it)
-
Right, that's the problem - your bugs are using the wrong story point field. You need all the issues to use the same Story Points field.
-
I've seen it raised a couple of times in JAC, but closed as "not in the foreseeable future"
-
That tells me the project has no issues in it. Now I'm very lost.
-
No, you can't do it on Cloud. Also, even if you have some javascript or script-runner on Server, all it will do is hide a field from display, it will still appear in searches, and the html that goes to the browser of the user. The only way to properly secure a field from users is to write an add-on (of a type that can't be…
-
The field will display "unresolved" when the field is empty. Can you tell us what this search returns? project = DIEN AND resolution is empty
-
Ok, that's perfect. Could you check these two next: * Nip into Admin -> Custom fields, and find the Story Points field - can you confirm that you only have one * Go to HT1-162 and HT-163, and check they have Story Point values set
-
They are a useful way to break up the issues in a project into related groups, and it allows project administrators to set the list of groups. As an example, imagine building a house as a project, you'll probably want to break things down a bit into things like walls, roofing, doors, windows, plumbing, electrics, gas,…
-
Access to any of the three applications (Core, Software, Service Desk) allows users access to all projects, because the projects and issues are the core of the product. This is because Software and Service Desk are not separate to Core, they are a layer over the top of Core projects and issues. To stop people using…
-
Sounds like an inexperienced admin has put the "resolution" field on the "create issue" screen. You'll need to get it removed before you create any more issues.