Nic Brough -Adaptavist- Expert

Yes. Team-managed projects are not really ready to be used by larger organisations or all but the most simple of independent teams.

Jira doesn't record that, other than as a line in the audit log (which is cleared down after some time)

Ok, so a post-function is of no use to you. You need a listener or automation that acts when a custom field is edited.

Welcome to the Atlassian Community! I'm confused, what makes you think the issue type has anything to do with sharing an issue with someone? (And what do you mean by "share"? Send them a URL for the issue view?)

I'd replace your field with issue links - they validate the issue exists at the other end and show information about it in the current issue. You don't need your issue picker type field, you're just making life complicated for yourself by (poorly) duplicating functionality that already exists.

Assuming you mean Jira, then the question is nonsense. The system has a premium licence, not users.

Because the suggested queue category is the same as to do or in progress depending on your process. It is too vague to be useful and not needed.

AI - oh heck yes. Not just creepy, but downright terrifying. Machine learning, not really. I think it can, and will, look creepy, but I don't think "expert systems", no matter how well they learn, will be. I think "creepy" implies sentience behind it. An expert system doesn't have that. A proper AI does. I'm <mumble> years…

Welcome to the Atlassian Community! Cloud and Server/DC are very different systems, and so are the Scriptrunner apps for them. I think it was the Team event in Barcelona just after we released SR for Cloud where Jon Mort opened the talk on how his team wrote it with "we started again, writing it from scratch". Server/DC…

However, other people have reported the display bug you are seeing, and it really does look like a bug (you're doing nothing wrong, not even mis-reading, I'm 99.99% sure there's something iffy happening with label fields in some Cloud systems)

Again, there's too little to see what the screenshot is of, so there's not a lot I can read from it.

No, it's not that granular. All Jira administrators can configure it, like any other system app. (The standard recommendation is that you've only got 3-5 admins, all of whom talk to each other a lot, so you shouldn't really need to think about restricting the admin access )

It's the other way around really, JSM is designed to insulate developers from end-users by putting an ITSM layer between them. The main idea is the JSM portal is the route to communicate with end-users, but the Agents in the JSM projects act as a gateway. The agents try to answer as many of the calls as possible, and then…

What do you mean by "ticket"? Do you mean the customer's request or the agent's issue that is paired with it? In general, the creator is the person who typed it in, the reporter the person who was asking the question (so when you ring your bank and tell them there is a problem, you are the reporter, but the agent at the…

Confluence is a wiki, its structure is built more freely than a fixed taxonomy, but it does have a load of stuff that does taxonomy-type things. * Your space and page tree structure is entirely free, it's not rigidly limited to a taxonomy. But it leans a lot on labels to group things together wherever they may be in the…

>should it not show correct figures even if few original estimates were entered at sub-task level. It is showing the correct figures - it is ignoring your sub-task estimates because they should not be there. >What happens if time is tracked on tickets where original estimates were not entered It tracks time on them. If the…

Very much so. It's also something that lets people like my lot get a foot in the door - the "fix" that I tend to deploy that I described above is a doddle to do with one of our products! When I first ran into Atlassian, they'd just opened up the "plugin" framework so people could write things to add to it, and they had a…

It's a security nightmare, let alone audit. To use a knowledge-base, either make the space anonymously accessible, or use it as part of an ITSM project (Jira Service Management has customers, who don't consume paid licences, and automatically get access to spaces set up as Knowledge bases)

Welcome to the Atlassian Community! https://support.atlassian.com/contact is the simple answer. If you are interested in geographical location, then the answer is "scattered across the globe (but still collaborating via Atlassian tools)"

Also, Company-managed projects do not limit the sub-task type by the parent type. Any issue type can have sub-tasks of any type in the project.

Sorry, we posted at the same time - my last comment was a response to the previous one. So, you now have three accounts. Atlassian accounts cannot have the same email address; it is the human unique identifier for them. I will talk here about account-1 having email-1, account-2 having email-2 and so on. But your last…

Sorry, I wasn't too clear on how to combine the new clause with your working query - glad you found it!

But you should never have a shared account, it breaches your licence, and can't be audited (it's illegal in most industries)

Welcome to the Atlassian Community! Moving an issue is not a trivial action, you could (and usually are) changing the whole structure of the issue. It's not like moving furniture from one house to another, it's like converting a terraced house into a detached one. There's no automation for anything but the most simple case…

That's because you now have three accounts. I can't tell what you are trying to do now. Consolidate them (dump two and use one)? Change the email address on one of them to a fourth email address? I am very sorry, but I am totally lost on what you're trying to achieve now. I think I know where you are, but it is not clear…

Yes, the time-tracking works fine, but the sprint estimates absolutely fail. If you're going to put estimates on sub-tasks that's fine, but they can't be sprint estimates, unless you automate something to accumulate them properly so that Scrum calculations recognise them.

Another thing I've always wanted - rid of the Epic Name field completely - it should be just the Summary (I know how it ended up that way, and it's a boring story, but the two should have become one years ago, Jira 7.0 at the latest!)

300k issue can easily be handled by a Jira with a 6Gb heap, that's not going to be the problem. I'm afraid you need to take a good look at all of the sizing of your systems and what your users are doing with it. How are you monitoring the JVM? Does the memory usage gradually creep upwards until it crashes and needs a…

I can't see anything wrong with your screenshot - you seem to have a perfectly valid value for GSS code for all the issues in it. But, there's too little to see what it is a screenshot of.

Welcome to the Atlassian Community! Yes, it's one of the four supported databases. See https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html for the current support version matrix (and hit the dropdown at the top right for other versions).