Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! The most likely explanation is that an admin has removed your permissions to use your project.

Admin gives you admin rights, not project rights. Please check your project rights to create issues.

You need to give Tableau the right address and connection credentials.

I'm not sure what you mean by "starting velocity". Do you mean the velocity that came out of the last sprint, or the the total estimate you committed to delivering at the start of the sprint?

Welcome to the Atlassian Community! I'm afraid this is not coming from Opsgenie, it's being added by Mimecast. There's nothing you can do in Opsgenie to stop it, it's happening after Opsgenie has sent the email. I always find email disclaimers amusing, as they're utterly pointless, and yet people still actually pay…

Welcome to the Atlassian Community! I know looking at a database is an instinctive fix for when you've got not-easy questions to ask of a system, but with Atlassian tools... don't. The databases are designed as data stores for the applications, they are absolutely the worst possible way to ask the system for reporting.…

Welcome to the Atlassian Community! How are you recording your rejections in Jira?

"since i got the the subscription suspended " - this implies you have stopped paying for the service or cancelled it. Either way, that will be the problem - a shut down system won't try to send email to ex-users.

Repeating the information does not answer the question. Please could you explain what you think is wrong with the email?

Welcome to the Atlassian Community! Epics need to live in a project, they are issues in their own right. To use an Epic, you set the epic link on stories. The project the story is in is irrelevant (other than the project permission to see the issue and edit its epic link field)

Nothing really. I'd suggest asking your admins why they've added duplicate issue link types!

Sorry, I forgot the most important point. Whatever you choose, make sure it is a version that is supported by your target Jira version.

The database landscape hasn't hugely changed over the last seven years. The short answer is you should use the database that you are most happy working with. The difference in performance between well-maintained and well-configured databases is negligble. If you really want to put them in order of "best" nowadays, it is…

This simply means that your network can't find the address behind the server name you have given it - https://stash.bbpd.io/***.git simply doesn't exist. It's a bit like writing "Bob, one hundred and eleventy twelve, turnip street, royston vasey, UK" on a mail envelope - the Royal Mail in the UK will "return to sender"…

Sorry, I should not have included the actual settings in my answers, it's misleading you. They are the values found before we corrected it. Yes, you should follow the docs, but you need to get all three of those settings right.

The category field has been there since Jira 4, when JQL arrived. (It is actually older, Jira 3 had it, but JQL made it searchable)

Welcome to the Atlassian Community! What do you mean by "deleted"? If an issue is truly deleted, it can't appear anywhere - every part of it is gone and there's nothing Jira can show on a board, issue view or report.

Welcome to the Atlassian Community! Go to your profile (the image you have for your profile towards the top right of your display) and (re)select Korean as your preferred language

Ok, that's a good reference, but you have not explained what you think is wrong with it.

No. A gadget on a dashboard is specific to the dashboard, they're not shared objects. There is a welcome gadget which has a global config, so it always gives the same text when it is placed on a dashboard, but that's because it is coded to look at a system-wide block of configuration.

Can you give us the whole script?

Welcome to the Atlassian Community! Moving an issue is not a simple task, but Jira tries to keep the process as simple as possible, and only asks for the required data it needs to change as you change the structure of the issue. It won't ask for a new status if the current status exists in the workflow you are telling it…

You can do this, yes, but why? Of what possible use is a list of roles of users in a project on an issue? It won't tell you what they can do in the project and it can and will change. I can't see any use for this, so I don't think it's worth going to look at the code you might need. What problem are you trying to solve…

Possible to delete - yes, but don't, it makes a complete mess. Returning them to the backlog - not if you delete them! Do you really mean delete?

Your screenshot is too small to be clear, but yes, you need to get all three settings right.

Check that you have permissions to restrict pages in the space settings. 스페이스 설정에서 페이지를 제한할 수 있는 권한이 있는지 확인하세요.

This suggests that your account does not have "create issue" rights in any project that you have configured the test management app to have tests in.

So where is this tally coming from?

Um, project category has been searchable since Jira 4 got JQL. It's not a "recent" thing.

It is the same answer. A human summary of the issue is the only mandatory enterable field.