Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! You do not validate anything in a post-function, it is too late in the change process to be checking something is valid. You need to write a condition if you want to block people using a transition, or a validator if you want to check what they are doing during the transition. You don't…

Welcome to the Atlassian Community! They are bits of code that run when you transition an issue. They run after the transition has been checked as valid. Jira has a number of them that run by default - one re-index the issue, another fires an event, another stores the changes to the issue, and so on.

I suspect they will have changed the settings on Outlook, removing or changing the script that is adding the garbage to the email

Welcome to the Atlassian Community! This is a complex one for my current employer because we're an Atlassian partner, and hence have a swathe of Jira systems and are helping out with a much much larger swathe of other people's Jiras. We are looking after Jira systems ranging from free to tens of thousands of users (there's…

Number fields only hold raw numbers, but their display is determined by your language and region settings. If I enter 1000000 into a numeric field, it displays as 1,000,000 for me, because English uses "," as the three digit separator. The field still only holds 1000000. If your number fields are actually strings, then…

You are looking at a team-managed project, which do not support transition screens. So you can't do this.

No. People need to be in your instance to be able to use it.

Please see https://www.atlassian.com/software/confluence/pricing (you've asked this question in a Conflunce area and tagged it with Confluence, so I assume you mean Confluence rather than Jira) https://www.atlassian.com/software/pricing-calculator will help you explain your costs for all of your Atlassian software though.

Add a transition screen to the "mark as done" transition in the workflow, and include the resolution screen in it.

It is possible to change the ports Confluence runs on, but you've got the two you need to open up for a default install. We can't tell you how to set up your firewall - it's not an Atlassian thing, you could be running any one of a number of things, and you have not told us what firewall you are using or how you have not…

You will be fine with any account that is not based in an area currently under the impact of the war, and not using IP addresses within Russia, Belarus, and large chunks of Ukraine that may be currently occupied, or at risk of being occupied. The main thing though, is that your account is not owned by an organisation that…

An "inactive" workflow is one that is not configured to be used by any projects. To make a workflow active, you need to associate it with a project. Team-managed projects do not use the global workflows. You can edit their workflows by going in to edit their issue types (each issue type will have a workflow button in it)

Um, you actually give the endpoint you need in your comment.

An email address is an address for a mailbox. If you do not have access to the mailbox, then the emails sent to the address are not for you. You will need to get access to the accounts mailbox to set it up as a dummy user. But, really, you should not be using service accounts to connect to Jira. Can you explain what you…

Start at https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/#jira-cloud-platform-apis

You would need to install a Sharepoint server on your own hardware, and then look for automation tools for it. As Jack said, this is not the place to ask, it's a forum for Atlassian users - most of us don't use Sharepoint, or where we did, we've migrated off it.

I think this is something that really needs to go to Atlassian now, please do that (and let us know how it works out)

Yes, this happens sometimes. A workspace admin only administrator the workspace (they may have many of them). Often, they are also a "site" admin, but not always. You need to talk to your site admins - these are the people managing your user accounts and also responsible for paying the bills. They can add/change/delete all…

Welcome to the Atlassian Community! Software projects do not have Requests, Jira has no choice but to drop that part of the issue when there is one if you move an issue from a JSM project to a JSW one - there's nowhere for it to exist. You should not be trying to clone the issues though - your agents should be using…

The easiest way to identify your admins is mostly "ask another human". Go to any board you're uncertain of, and look at the user icons at the top right. Board Admins will have a couple of blue arrows on their profile picture. You may need to click on the + to the right to expose all the board users. Board admins will…

No, you should probably use one account, the one with access to your source code.

Welcome to the Atlassian Community! Yes, attachments can be edited.

Welcome to the Atlassian Community! Deleting a project (whether full delete or move to trash) only affects the issues in that project. I suspect the vanishing issues is probably a coincidence - someone else reconfigured something at roughly the same time you were trashing the projects. The two cases where it would not be…

Heh, no, that is not a mis-translation to me, it's Jira-speak not translating well between Spanish and English. You could run things with filters that explicitly include only the issue types you want to see, or exclude the ones that do not. For example, "issuetype in (bug, task, feature)" or "issuetype not in (tech-task,…

Automation can do this, yes. (I'd be a bad Adaptavist if I didn't point out that there are other apps that can do it too. But I assume your "possible without JMWE" means that you are looking for an app-free solution)

You can't do this during a transition, because a transition has a fixed endpoint that you cannot change after you've decided to go there. But you can do it before the transition starts, or after it ends. The two tricks are both workflow based. I'm going to imagine a part of your workflow and try to keep it simple. Let's…

Because humans are bad at negative logic. When you ask a logical system "show me things that are not X", humans don't understand that a thing has to have an attribute to compare. Logically, "show me the containers in the 'fridge that do not have curry in them" will only show me the containers that have something in them.…

If you don't have a mailbox, then you do not have an email id. You've got an email address that either belongs to someone else, or does not exist. You will need to be able to read your email mailbox for any email you want to verify.

Multiple boards can work very well, if you set them up carefully with a holistic view of the whole process. Using your example status, I would imagine a workflow (simplified, I'm imagining a person would move an issue into the next status when they've done their work on it, but I imagine a real workflow would be a bit more…

The recommendation was always "disable users who leave, if they have any footprint in Jira" because deleting them means destroying your history, which may be needed for audit or compliance. That still stands, but the important bit is the "footprint" - it's fine to delete a user if they have not touched any of your issues,…