Nic Brough -Adaptavist- Expert

That's not strictly true. In Jira speak, "mandatory" means that a field must be filled. From the initial creation, through transitions, and during edit. Resolution is not mandatory - you don't have to enter it to create, edit, or transition an issue. But when you put it on a screen, it always defaults to a value, and there…

@Rod Bergmans - I'm afraid not. DC licences start at 500 users for most systems, although some people have managed to wangle 250 at the lower end.

What do you mean by "option is already closed"? What does that look like?

Do you mean sub-tasks of the Epic, or issues (stories) linked to the epic as part of it?

You need to use two workflows, one with the screen used for the transition, and one without it. You can then set the workflow scheme to use the two workflows differently for each issue type. Or, you could just have one workflow, include the transition screen, and you'll find that the field is not shown on the transition…

Welcome to the atlassian community! No, what you are seeing is down to another user or script, it is not you, or Trello. It could be a virus on someone's machine but the most likely explation is a script. 

The field context applies to the issue as a whole. You can hide a field in the field configs, and you can not put them on any screen, but the thing that matters is the field context. If your field has the context, it's on the issue, no matter where it is visible. I can not be sure of your set up, but it sounds like you…

Welcome to the Atlassian Community! You will need to set up your build environment so that it includes the missing package. We can't tell you anything more than that, based on a snippet of error and no other information.

What do you mean by "unable to create a sprint board"? What happens when you try to create a new board?

No, it's a good thing. I've seen far too many Jira systems either with horribly useless reporting, or regularly being taken down (non performant) because people have tried to use the database for reporting.

You'll need to convert the return value from milliseconds up to days (I think it's milliseconds, not seconds) - divide by (1000 * 60 * 60 * 24)

No, it's not possible because Cloud gives us no way to write code that could read the database.

No, you can't get rid of the number in the url, JSM needs it to provide a unique url for each portal. See https://community.atlassian.com/t5/Jira-articles/Changing-your-Cloud-site-name-url/ba-p/1905210 for discussion of changing the "var" part of your site name.

How have you created the scripted field? If it's with Scriptrunner and used the scripted field functions from that, then can you check that you have set it up with a number template in Scriptrunner, and changed the "searcher" to either exact number or number range.

Welcome to the Atlassian Community! What would these buttons do?

No, the column widths are fixed, you can't change them.

I think your arithmetic doesn't match the time tracking settings. 310,500 seconds is 86.25 hours, so that bit looks right, but an 8 hour working day turns that into 10.7 days and a 5 day working week makes it 2.2 weeks. I suspect you don't have Jira set to a 5 day working week, as 1w 3d would be 10 days for a 7 day working…

First hit on search engines seems to be https://support.atlassian.com/opsgenie/docs/opsgenie-edge-connector-installation-packs/

I'm afraid that does not tell us enough about the problem. What "SQL+JQL" driver are you trying to load? Have you asked the vendor about it? What are the errors you are getting in the log when you try to add it? (Please read <jira home>/logs/atlassian-jira.log for the time you're triggering this error)

Welcome to the Atlassian Community! No, there's no way to re-arrange the field areas on this screen. The sub-task section only appears after you have added a sub-task to the issue though, it'll vanish if your issue has none.

There is no way to do this - the closest you could get is removing the ability to comment, but that can not be done conditionally based on a field, it would have to be done by having two different issue types.

This suggests that your admins have places restrictions on the workflow, or that the project does not have issue types that you can move the current issue to (either because there are no other types at the same level, or because the others are configured to use different workflows or fields)

Welcome to the Atlassian Community! Automation works (mainly) with issues, it doesn't have admin functions like user updates. You will need to look to apps to do this sort of thing. If you've got Scriptrunner and a Server/DC instance, https://library.adaptavist.com/entity/deactivate-list-of-users would be a good place to…

Neither of those have the version 2 editor - that was in versions 3, 4, and 5. The editor changed again in version 6, and hasn't been changed a huge amount since. I think you need to explain what you think the "version 2 editor" really is?

You don't need to worry about the "changed" part of this. When an issue rolls over into the next sprint, it does not lose the information that it was in the sprint (that your team need to talk about where they failed to complete what they said they would) You can find these with the query project = "Project Name" AND…

Welcome to the Atlassian Community! Trello uses Atlassian accounts for its user access, and those can only be logged into via a single email address, because they use the email is considered a unique identifier. So the answer is "no" But changing the email on your Atlassian account will not lose you anything, it really…

@Michael -Get Report- - no. Nope, nopeity nope nope. For the last four months, I've been paid my salary by having to correct ******* awful code written by GPT. It's a sodding nightmare, GPT and the others have no idea. I really want them to stop, so I can go back to doing a real job. Stop it. It's wrong. But that is highly…

I'm afraid Jira does not yet support SR's abilities to do a lot of things in Cloud, but we are working with Atlassian to try to get this sort of stuff added.

Welcome to the Atlassian Community! Generally, no. Sub-tasks do not have sprint estimates put on them, as they are not sprint items, and hence Jira ignores anything you do put on them. The estimates that count towards the velocity of a board are the ones you put on the sprint items (stories). You can script or automate a…

Not really, why would you want to?