Comments
-
Hi @Petr Novotný , could you share the config of your automation rule (trigger, condition, action) in a screenshot?
-
Hi @Julian Reichle , are these pictures uploaded as attachment on the Confluence page of the Knowledge Base Space? Or are they embedded from another location? When you say that some users cannot see the pictures, are you talking about Agents (with a JSM license) or Customers (visiting the portal)?
-
Have you tried to include the Task Report Macro on a test page and try to check the action items from that page?
-
Thanks for sharing the process for the new user management experience @Dave Meyer !
-
Just noticed the tab in the Atlassian Access product (after more than a year), thanks for sharing!
-
Hi @kchoi , Can you show us how you set up the automation rule (trigger, condition, action)?
-
Hi @Noreen Zinat Choudhury welcome to the Atlassian Community! What type of custom field is 'Productivity'?
-
Hi @Armando Villarreal Lemmen Meyer welcome to the Atlassian Community! Have you removed the tasks from the originating page mentioned under the column Task appears on (which is not on your screenshot)?
-
I agree with Dirk, switch to the Free Plan once you can.
-
Interesting thought, would a Standard Plan with 0 Agents still cost anything? Or do you need to switch to the Free plan once you have maximum 3 agents?
-
Hi @miroslav-odstrcilik , if you remove all users from the group jira-servicemanagement-users-(sitename), then you will no longer have paid licenses for JSM. Site Administrators will keep the possibility to manage JSM projects.
-
Hi @Faten.Kutbi have a look at this page for more info: https://support.atlassian.com/jira-software-cloud/docs/set-permissions-in-advanced-roadmaps/
-
Hi @Stefan Müller , you can link/limit Accounts to Projects. So, for example, create a non-billable Account and link it to a specific Project so that Log Time can only be done for this non-billable account. If there's only 1 Account linked to a certain project, then you won't have a dropdown list.
-
Hi @Maktumhusain Taseeladar , Do these custom fields have any context restricted to projects?
-
Sorry, this was for Server/DC. Can you try: resolution = Unresolved AND fixVersion in unreleasedVersions() fixVersion singular
-
In Advanced Roadmaps you enable custom fields, then you add the custom date picker field.
-
Hi @Daniel Gatere , please try the following JQL: resolution = Unresolved AND fixVersions in unreleasedVersions
-
This is a permissions issue. You'll need to ask the Space Administrator to grant you the Add Attachments permission for the designated space.
-
Hi @Ashish Kumar welcome to the Atlassian Community! Are you able insert a file/image via the browse option rather than copy/paste?
-
Hi @Eran Roiter welcome to the Atlassian Community! The (basic) Roadmap doesn't support custom date fields. It uses the Start date and/or Due date fields.
-
Hi @Axel , custom field configuration schemes (contexts) are defined within the custom field. You cannot share contexts between custom fields.
-
Hi @Maryann Fitzgerald , when talking about Admin, do you mean Board Administrator? Does the board filter have issues from more than 1 project?
-
@Varad Pingale Please implement this for Data Center as well.
-
Whatever happened to the Atlassian Company Value Don't #@!% the customer? "Customers are our lifeblood. Without happy customers, we’re doomed. So considering the customer perspective - collectively, not just a handful - comes first."
-
Hi @Irem Sayil welcome to the Atlassian Community! Have you checked your outgoing mail settings? See: Configure Jira Cloud to send emails on behalf of your domain
-
It may have something to do with mixed HTTP/HTTPS content, but I'm not sure.
-
You'll need to create the Automation Condition yourself. See Jira automation conditions for more info.
-
Hi @Graham McCartney , you could use Automation with a JQL filter updated condition to send a notification.
-
Hi @Neil Green , are there possibly any workflow functions (conditions, validators) or transition screens preventing users to do this?
-
Hi @Rubén León Herrera , Without Atlassian Access, a user wil receive an Atlassian Account with a new password, that is self-managed. You won't be able to migrate passwords from you Server instance. When you adopt Atlassian Access afterwards, connect it to an IdP and enforce SSO, the current AD password can be used…