Nic Brough -Adaptavist- Expert

I'm afraid not, you need to use the API key route now.

There is no alternative inside Jira. Bulk edit is for, well, doing bulk edits. From the outside, you can script something to do your bulk edits in small fragments, so it doesn't overwhelm it, but that's about the only thing you can do.

That's exactly what bites me on the bum too when I'm trying to do clever things with properties! Well spotted!

Welcome to the Atlassian Community! Seriously, don't bother. The Jira database is not remotely designed for any form of reporting, it is a data store. You are wasting your time trying to use SQL to report on your Jira data. The best case is that you'll get an inaccurate report. The worst case is that you'll take your…

Are they enabled users (Can you get one of them to log in and try to create an issue in the project - not to the end of the process, just as far as getting the popup for entering the fields)? Could there be duplicate accounts with the same email address? 

That suggests you have a line that names a sub-task issue type, but has no parent ID filled. One thing to try is filling in every line with a parent id - for the issue level issues, use their own id as the parent (jira should ignore the field for issue level issues) Re-using my example with that tweak, you would import: *…

If you've chosen Kanban, then the defaults will be not to put an estimate on screen for you - Kanban doesn't do estimates. (Well, actually, it does, but it's calculated - one card = one unit of work. Each card is an estimate unit and they're all the same "size") I suspect that you've accepted the default settings and…

NO! Never put the resolution field on an edit (or create) screen.

Indeed, the whole point of Epics is that they gather together stories that can be done in a sprint. You use an Epic when you've got a collection of inter-related stories that add up to something you can't possibly achieve in a single sprint. Epics are not sprint items.

That does not quite answer the question Mohamed asked, but it's a start. I think you are saying that you want to send an email when someone updates a field on an issue, changing it from <empty> to <something>. Is that right?

I don't see any unfairness here, only a bit of inconsistency. If they've changed the (maximum) number of questions from 70 to 75, then someone absolutely should update the documentation to tell us that. On the scoring, I suspect the inconsistency is a simple one - the exam system is giving you a percentage rounded to 1…

I am not happy that I have to day this, but your comment does not make any sense. I can not see what you are trying to say (there is something there, but I can not read it from your writing)

Yes, and I think you're absolutely right about the "issue picker" being limited to the same project. But, is is a limitation. Issue links are the best option in every case, except when your project owners want to limit you to link to certain things like the current project. I do not think we can opine without knowing all…

Ok, that's suggestive of a memory leak. I'm afraid you're going to need to dig into what the JVM is doing - what is not freeing up the memory. That's not a fun thing to do - JVM investigations are complex and arcane. Increasing the memory heap (by maybe 256Mb at a time) may help without needing proper investigation, but if…

Ok, so I'm now even more confused, as you're not doing what has been reccommended You say "Very strange mechanics. I don't see the logic at all.". The logic is simple - you have created several accounts, and not set them up for access to the same things, so they have different access to different things. The email change…

Welcome to the Atlassian Community! I think you need to ask your IT support people about this. The question has nothing to do with Atlassian stuff.

Welcome to the Atlassian Community! I think you may be in the wrong place, this does not seem to have anything to do with Confluence, or other Atlassian systems. Have you clicked on "help with doc systems (hosted by Atlassian)", instead of "help with the software"?

I'm not quite sure what is happening here: You say "When you make the knowledge base visible to all logged in users, Groups A and B could both see each others spaces" A knowledge base is a single space in Confluence. If you make it anonymously available, then the world can see it, but it has no effect on how group A and B…

This means that Confluence has run into a problem for which the developers have not managed to catch and write a helpful front-end error report for. You are going to need to do what the message says - ask your administrators to investigate the errors in the log.

Welcome to the Atlassian Community! There's a somewhat cynical answer to this - business projects are supposed to be basic and simple so that when someone needs more power, they have to go buy Jira Software or Jira Service Manangement. The less cynical answer is just that "business users don't need, or want, complicated…

Yep, I've drifted away from "how" there. But it's what I said earlier - go to Admin -> Issues -> Custom fields -> your user picker -> edit context/defaults, you'll see an option for "filtering". This will let you add roles and groups to the filter. So you can say "this picker should list the users who are: * in the role of…

It's actually horribly complex to work out permissions for a project/user combination - it's now the very first thing you look at when you're trying to performance-tune a Jira system. It was in second place until Jira 8.0 did a lot to help with the old first place. The user-picker field would be a performance nightmare if…

Argh no. ITSM is about planning, delivering and supporting IT services. Without an ITSM "layer", you simply can't function. Simple worked example - you put a developer in a room with a bunch of financial traders. Can that developer handle every single IT related problem they might throw at them? From "power cut", "server…

Yep, your non-admins may be able to trigger some script actions, but only ones that have been set up for them by your admins..

One of your admins has added a field called "Delete" to your system, and made it mandatory, so you need to fill it in before you can create an issue. Either get rid of it, or get it added to your create screens so that people can fill it in.

It may be worth understanding the process Jira goes through when it gets an email: * It looks at the email address in the "from" field in the email header * It looks at its list of users, searching it for a user with that email address * If it doesn't find one, it assumes the user is not a valid Jira user, so they can't…

Welcome to the Atlassian Community! Jira has dashboards which can help you with this. They're a collection of gadgets that you define that show you data in different shapes. So, to start with, create a dashboard for your programme. Many of the gadgets you can use have specific inputs like a project, agile board, or user,…

Welcome to the Atlassian Community! Your file looks technically correct to me, but I have a nagging doubt that it doesn't like the empty issue id on the sub-task line. When I do imports with sub-tasks, I've always done it with the issue id populated for all issues, even though I really don't need it on the sub-tasks. So my…

It is still the case, there's not a lot built into Jira to help you with it. However, there are now a lot more apps that can help you move projects between systems. There's a been a handful (Project configurator, Configuration Manager, etc) for years, but over the last couple of years more have become available, including…

So it means "in progress" to you. The reporting you are talking about is something that should be being done at the status level.