Nic Brough -Adaptavist- Expert

Your screenshot is too limited to see what you are doing. If, however, it is the one from the "issue options" menu (not the workflow), then I'm afraid I have to tell you that your BI team are talking utter *******s. The delete from the tools menu destroys all the data in the database related to the issue.

The most likely problem is that someone has reconfigured your issue types so that they are no longer compatible (or, possibly, given the message, removed the issue type from your project) Why do you not just change the incoming email setup so that it creates incidents instead of the wrong issue type?

Welcome to the Atlassian Community! Talk to your project admins, they can create whatever components you want, so you can then add them to issues.

I can not think of another way to explain this. If you delete an issue in Jira, it is deleted. The data is removed from the database. That's it. There's nothing more I can explain about issue deletion. The only thing I can say that is related is that whatever process you think is "delete", it is not. It is something else.…

It depends entirely on how you choose to use the key and name. There are no "issues" you'll get from the software, unless you have chosen to use it differently to the way it is intended.

Again, the issues you are seeing have not been deleted. If they are in the database, they are not deleted. Jira deletes the whole issue when a human hits the delete button, it kills the current issue record, the comments, the custom field data, links, the hierarchy records, the history and the rest. They are gone. Rows in…

You will have to search for and delete the data you want to destroy.

Welcome to the Atlassian Community! A board is a view of a set of issues, so the simple answer is "set up your boards to select what you want to see on them" If you own a board, this is, of course, a doddle. But for boards you are not the admin on, you have to ask the admins to make changes. There is every chance that the…

If an issue has been deleted, then it is not in the database anymore. Your team have not deleted the issue if you are still seeing it in the database. I think your Tableau settings are broken (they almost always will be if you've connected it directly to the Jira database)

There aren't any. Epic is a level in your hierarchy that is unique. Epics can't have a child Epic. If you have defined a hierarchy more complex than "Epic -> Issue -> sub-task" using Structure, Advanced Roadmaps or something else, they you'll need to search through the different layers, but none of them will let you do…

If an issue has been deleted, it can't be counted - it's not there any more. So your query works fine without any deleted marker. In fact it only works because you don't have a deletion flag. This case proves the point that you don't want a deletion marker! The query "issuetype = epic and status = done" answers that…

No, the point of an issue tracker, documentation system and source code repositories (and the rest) is not to lose data. Deleting a user's data just because they leave is the complete opposite of what Atlassian systems are for. Data will only be deleted when you explicitly choose to kill it off.

Ok, that's great context in which we can try to give you a better answer, but it does open up other problem areas. A flag for "issue deleted" tells you no more than "issue is not there any more", If you think you need a record of deletion, then your approach to your analysis is wrong, you are going to get the wrong numbers…

Yep - they got a new licence for the missing app.

Your instinct to reach for a backup is exactly right. I would want to start with a clean installation of the software, in a different location (ideally different server - nuke the old one from orbit, it's the only way to be sure) Your malware attack might have damaged the data in the database, but it won't be able to…

You know an issue has been deleted when you can't see it any more. You don't need a flag. It's a bit like putting up a sign that says "please don't read this sign" - utterly pointless and tells you nothing more that you found out by not having the sign in the first place.

Don't mark this right, it's not an answer. As you have volunteered that you think you've raised it in the wrong place (I wish more people would pay that much attention!), I've moved it. Please yell if you think I've got the wrong destination!

Welcome to the Atlassian Community! Deleting an account only deletes the account. Confluence will put the users personal space in the bin, and all of the systems will throw away local personal information, but no, all the stuff you're trying to track, share, code for, and report on will be left intact. It'll just show that…

Through the payment system that is in the site admin, not the product admin. The last time I looked at a renewal, it offered me the option to pay for the next year's subscription several months ahead of my end-date, but that was for a small 50 user system. I don't look at larger systems, I work for a partner who has a…

Yep, exactly what @Radek Dostál said. I can only like their answer once!

Welcome to the Atlassian Community, and Adaptavist! To use a lot of Atlassian systems, we use an Atlassian account. These are either owned by us as an individual, or they are "claimed" by the organisation that your email belongs to. I've got a personal one I use to post here, but you might also see posts from me from an…

What problem?

The sigma symbol is used in the field of mathematics (and hence arithmetic as it's a small sub-set of mathematics) to say "sum of the following things". In Jira, we've got a few numbers that we put on issues, like original estimate and time logged. These are sometimes used to give us the "progress" field. The sigma kicks…

Thanks for giving us the info we need. It is one of the things I thought it might be - your network connection is not able to reach all of the servers your Cloud system is based on. This might be on your side, with firewalls or failed DNS services getting in the way, but it may also be a service in between your network and…

The requests have been dropped because they're asking for a technical fix for a human problem. The real fix is to have administrators who understand what they are doing, not have code block them from doing their job.

Go to https://my.atlassian.com and close down the trial.

It is what it says it is - your trigger does not select any issues to work on. The rest of the automation does not know what issues it is supposed to be amending.

The REST API does not yet allow for this administrative task. I'm afraid your admin is going to have to slog through the permissions for every space.

Welcome to the Atlassian Community! Where are you performing this search?

What are the notifications they are getting? Does the history show changes to the issues that would trigger these notifications?