Rebekka Heilmann (viadee) Community Champion

Try open the Link in an incognito Tab. It should open the Log In page and then work normally. There is some other Atlassian pages that are bugged like that (Certification page for instance)

Some words on the basic concept: Projects contain issues. One issue is only ever part of one project. Hence the unique ID with the project key. Boards are views of issues. Boards can show issues of one or more projects or even a subset of those issues. That is all controlled by the board filter. People have access to…

Hi @Sergio M. Gard You can't. I guess you have a Scrum Board that shows Issues from one project? (That's the default). You need to add the person to the project by assigning a project role, such as user: Add users to your project | Jira Work Management Cloud | Atlassian Support

You could check the Audit Log under Settings > System Oftentimes automatically created fields will have a proper description, but I guess you already checked Settings > Issues > Custom fields ? 

I've not found any definite information on whether JSM Data is included in BYOK? Can you shed some light on it and maybe add it to the BYOK FAQ?

I am assuming that all this is for one specific project? Have there been any changes to the workflow? In order alert listeners on the "Issue created" Event, this event needs to be triggered by the workflow transition. That is the default behaviour but can be changed manually. If the screenshots and tests all regard the…

You'd have to check additional settings, if you want your whole Help Desk inaccessible. Go to JSM Settings (Product Admin Settings) > Products > JSM > Customer Access Under "External" remove the checkmark from "Allow portal only accounts to be created"

My best guess is, that you switched the system's default language from german to english at some point... or is your user account in English and System is in German? Either way, you probably need the Atlassian support. They might be able to change the description texts into English, if they've not been translated…

Hi @[deleted] you would seperate Service Desk projects based on Customers (the people who open requests), Agents (the people working on said requests) and related topics. The only way to restrict one and the same customer to create one type of request but not another is to have them in seperate projects (in Standard JSM…

Are you sure you are creating a "Linked" Issue and not a Subtask/Child? Assuming you are using cloud, I have tested it in my instance from a task in an active Sprint. It doesn't even "prefill" the Sprint Field when visible and creates the new issue in the Backlog automatically.

fastsupport@apcoeasycare.onmicrosoft.com is an email adress. apcoeasycare.onmicrosoft.com is the domain of that adress. That is the part you need to claim, if that is your companies domain. For instance, other Service Teams in your company would have slowsupport@apcoeasycare.onmicrosoft.com…

Yes, assuming the infos are in issue fields? You can access the fields with smart values: Smart values in Jira automation | Cloud automation Cloud | Atlassian Support Example below: Hello {{issue.reporter}}, your issue {{issue.key}} has been resolved. Have a great day!

According to several other posts in this community, assigning products only works per user invite for Managed Accounts: Solved: Can't add product to managed account (atlassian.com) That's if they don't have product access to begin with. I think we solved that issue by AD groups -> all our users are in one of three synched…

To hide the portal * go to your Service Desk "home page" (www.your-jira-site.com/servicedesk/customer/portals) -> not the specific project's portal, but the parent page * Click on "Customize" * Edit home page Layout * Find the portal that you want to hide * Click on the "Eye"-Icon to hide For your user question... no idea.…

To do what? What do you want to import per csv?

Hi @Jordan Graves it sounds a bit basic, but are you already using Versions? In the Versions tab you can see unresolved Issues (incl. Bugs) connected to that version.

Hi @Kelle Foreman You can use Jira Automation for that. Trigger: Issue status changed (or field changed and check "Resolution") Action: Send email You are free in who to send what message in Automation and just need to find the right trigger/condition. Note though: There are limits on Rule executions now, so depending on…

Hi @Samuel Geurts Great question! Actually, there is a bit of a difference. The "Issue view" is connected to only one request type and overrides the Screen of the Issue Type (to a certain extent, that's where @Nic Brough -Adaptavist- 's explanation comes into play ). You can create issues in a Service Project without…

Hi @Gustavo Gabriel Riva The issue ID is a sequential number per project provided by Jira without any extra work ;) what do you need extra numbering for?

Hi @Phil Bustin just to be clear on some concepts in JSM: JSM works with Issues and Workflows the same as Jira Software does. So Issues are shown on Screens that show fields, have a Workflow and so forth. Requests are what users open trough the different channels. Requests are mapped to an Issue Type, so once a Request is…

hi @Phil Bustin go to admin.atlassian.com, pick your Atlassian Org and go to Billing. You will see all your products/sites and the available as well as the taken licenses.

You are currently using a team managed project. TM projects behave differently than company managed projects and have different options when it comes to configuration. You cannot change what you can see on the cards in TM projects. Have a look here: Manage and administer team-managed projects | Jira Software Cloud |…

Hi @Raul Rodriguez Can you screenshot whatever you want changed? You are saying Dashboard, but Cards and columns are usually only connected to "Boards". Dashboards are a collection of Gadgets, usually some type of reports or filter results. Boards are the ones with the columns, that are connected with one or more projects…

You'll find it under Issues > Collectors

Sounds like a problem that the Atlassian Support can help you with, as they can get access to your instance and the user's account. But maybe someone else in the community already had a similar issue - just thinking, as there is a lot of new posts every day and no answer after two days, the Atlassian Support is probably…

Hi @Kevin Shaffer in Standard Jira, you could use a Transition validator in your workflows, to make sure the reporter has a certain permission: How to restrict the creation of an issue based on issuetype | Jira | Atlassian Documentation Your project team would need a permission that your "customers" don't have and then you…

Perfect :) glad i could help. Please accept my answer as "solution" so other community members know your question has been resolved and will find an answer in the thread, if they have the same issue

Have you looked into the issues' history?

Cool - if your issue is resolved, please accept the answer as such, so other people in the community can see your question has been answered and find the appropriate solution here.

You don't need a Sprint ID. Using the "Active Sprint" function as you did in your screenshot works perfectly fine - at least in my case ;) But sure, you can try that out. But maybe someone else in the community had your issue before and will be able to help more than I.