Nic Brough -Adaptavist- Expert

This is going to sound condescending, for which I am sorry, it is certainly not meant to be. Are you sure you have a sprint called simply "152"?, and that there is at least one issue you can see in it? I recently got bitten by a sprint called something like " 152" - the JQL didn't offer me it in the auto-complete when…

This is one of the many quirks in Jira that most of us don't find until someone points us to it. This subject was one of the very first questions I asked of the Community, as it was back in <mumble> Assigning an issue is not really an "edit", even though you can do it while editing an issue. It has its own path and its own…

"Bother!", said Pooh, as he completely forgot about issue security when writing his answer. If the query I gave there doesn't return all of the 33 issues, then you've got an issue security scheme in place which is stopping you seeing them. You'll need to talk to the project owners about getting yourself added to the…

Welcome to the Atlassian Community! This isn't something the community can talk about, you should go direct to Atlassian about it. If you have an existing commercial licence for one of their products (not free or starter), then pop over to https://support.atlassian.com/contact and raise the question there. If you do not,…

You'll need to talk to your admins - they will need to add the screen (or the field to the current screen) in the workflow, so that the user is prompted for it. Or just the validator I described.

But the updated field is telling you when the issues were last updated, right?

I can't see a bug there, but I'm not entirely sure what I'm supposed to be looking for. If something starts on a Saturday, it's part of the previous week, no matter whether your week starts on Sunday or Monday. But I would want to check what the date settings are - go to Admin -> Look and Feel and check what the setting…

We can't tell you that, you'll need to talk to the administrators of the proxy to find out what it is doing. The server (not Jira) admins of your Jira server should be able to tell you what the outgoing proxy settings are - they would have had to add them to setenv.bat. (if it's an incoming proxy, they will have had to…

A big reason for archiving is actually to remove the content from the searches! That's why you can't default it - there's no point in archiving pages if you are going to carry on searching for them.

What email hadler have you configured? It sounds like you are using a "create issue from email" handler, and what you really need is a "create or comment on issue from email" handler. If you're using a create-or-comment handler, then the rule is "the first issue key recognised in the subject will be commented on". If it…

I think you're asking this in the wrong place. Laravel is a PHP framework, and we are an Atlassian community. Atlassian software doesn't use PHP, let alone Laravel. I suspect you've followed a link for "help with documentation system (Atlassian's Confluence)" instead of the link for "help with Laravel"

Well, just as a picky point, the format MM/DD/YYYY is always incorrect and should never be used, despite what North Americans think. But that's not the point. Yes, I suspect you have hit a bug that needs reporting to Atlassian. There is one other thing I would want to check before reporting this - what are the browser's…

@Anne Saunders - the poop emoji reminds me of an older version of Jira. It used to be a good way to test if a Server/DC install had been set up with a badly configured MySQL database! Nowadays, the admin health checks just tell you, but the number of times I've had "my content won't save / render / export" because it's got…

My mother's side of the family can all cook. Even me. I protest that I can burn water and set fire to a salad, because I get it badly wrong sometimes. But I can, and do, cook decent meals for my household, most days. My father's side of the family are more "meat and two veg". Granny started boiling the Christmas sprouts on…

I suspect there are 33 issues that are sub-tasks, ones that your query is not finding. Instead of naming the issue types you think are sub-tasks, try issuetype in subtasktypes()

You would have to do this by editing the database, but you'll find that fails as the updated date is recalculated from the last update made to the issue in a lot of cases. Why do you want to tell lies about the last time an issue was updated?

Um, run the installer? Your problem is not with the content of the database, it is mis-configured, so Jira can't use it.

It's quite a simple choice at the moment - team-managed projects simply aren't built for collaboration, they're only suitable for the cases where you have one team working on something and no other team will ever do anything other than have a quick look at the odd issue in it occaisonally.

You can see most of that from the sprint reporting built into Jira. There's no way to send reports via email though. The points-per-person is not in any reports because that's not what points are for. The points are for estimating what the team can do. Individuals are not supposed to be measured (and, in fact, it's illegal…

If you are going to be buying Jira Align, you will have had to go the Atlassian Align team and engage in a full sales and setup process. While the pages Stephen pointed you to are an introductory demo, they're quite light, and if you want something more in-depth, you should talk to the team who are engaged with Atlassian…

Take away their permission to comment or edit issues then. Taking away useful links is not going to help prevent their micromanagement attempts. You are looking for a technical solution to a non-technical problem - you need to get your people to stop trying to micromanage things, not just stop them seeing stuff.

>This generic user is present in assignable issue permission scheme and can not be removed from their Then you can't do it. The only way to block them from being an assignable user is to remove them from the permission that lets them be an assignable user..

Scriptrunner for Cloud does not yet have this functionality (we're working with Atlassian to enable it - the problem is with the Cloud UI, not Scriptrunner). There is a beta in progress, and we expect to be releasing it soon.

See the answer you commented on

Add a validator to the "close" transitions in your workflow, they can check if a field is filled or not and prompt the user for more data

Cloud is a service, high availability is part of it and not something you, as a subscriber, needs to think about.

You'll need to set up some form of automation that can use your field to decide on an issue security level to set. See https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Welcome to the Atlassian Community! See https://www.atlassian.com/trust/security/data-management

Welcome to the Atlassian Community! There are two standard ways to do this - have a transition screen on your "close issue" transitions that include the resolution field, so the users get to set it, or have a post-function that sets it. You will also want a "clear resolution" function on any re-open transitions.

It can be updated automatically. Automation, scripting apps, or external functions can all change custom fields. What are the rules you want to set for the updates?