Comments
-
Hi @Susan Cain, Welcome to Atlassian Community! You can limit the comment by adding this to the end of it: .abbreviate(200) This will limit it to the first 200 characters.
-
Yes, the subscription should still work, it is tied to the filter, not the user/admin that created the subscription. You can follow this KB to check that the email has been sent for an existing subscription.
-
Just replace the asset object with your custom field like this: {{issue.customfield_17913.Name}}, this will get the name of the object instead of the key.
-
Hi @Richard Hayes, Welcome to Atlassian Community! What smart value are you using? Since you say that you get the key instead of the name I would assume that you are using something like this: {{issue.asset object}}. If so that is expected and you would have to use the dot notation to get the name, like this: {{issue.asset…
-
Hi @Ásta Hrönn _RdN_, Welcome to Atlassian Community! Currently this is not possible in the portal. The similar requests feature is currently only visible to agents in the project, and as far as I know this is not something that is on the roadmap to make it available in the portal.
-
Hi @Keri Lilly, Welcome to Atlassian Community! It is possible, but you would need an app that extends JQL in order to do it. I have used JQL Tricks and Enhanced Search (Scriptrunner) in the past do this, but there are also other apps in the Marketplace that does this too.
-
Hi @Ignacio Rios, Welcome to Atlassian Community! The epic link field is being replaced by the new field called Parent, and you should use that field instead.
-
The short answer is no, currently you cannot modify the sign-up email that is sent out.
-
The short answer is no, there is no setting that would allow you to disable the option for the customer to turn off notifications.
-
Unless you have an app installed that can restore deleted issues before the issue gets deleted there is no option to restore it. Once it is deleted it is gone.
-
That all depends on how you configure your security scheme. But you would need at least two schemes, one that is allowing a wider group to see the tickets and one that limits the access. You can then use automation to set the security level based either on the request type or something other in the ticket that determines…
-
This is expected, agents will only see work items in projects that they have access to. Even if they are able to link the issues, until you give them access to for example the HR project as a collaborator or agent they will not see the ticket. I have a similar set up in our HR project, other teams can see…
-
Yes, the change will be handled Jira when you publish the workflow, so you do not have to do anything other then setting the new status. This is what it looks like in the new workflow editor, it defaults to a status in the same category, but you can select a different status if you like. Once you click Update workflow Jira…
-
Yes, any changes will affect all work items that are associated with that workflow. So for example if you remove a status and replace it with another one, when you publish the workflow you will be asked which status replaces the status that was removed.
-
Hi @luis valle, Welcome to Atlassian Community! Work items on a board is based on the filter that the board is using, so all you would have to do is change that filter ti pick up the work that is submitted from the collector.
-
First of, I do not work for Atlassian, just like you I am a customer. You are correct, Atlassian support do not have a phone number that you can call, but they now do have a chat function that can be used. Since you are on the premium plan I would just try an escalate the ticket, there should be an option for that if you…
-
Hi @John Hall, Welcome to Atlassian Community! I am sorry that this has happened to you. Since this is a community for Atlassian products, would you mind telling what your issue is about? Is it about an Atlassian product and you have an open ticket with Atlassian support? This community is mainly made up of customers that…
-
Hi @Gladwin James, Welcome to Atlassian Community! No, project Id and project key are two separate identifier. The easiest way to find the project Id is to go into an issue in the project and click on the three-dot menu up in the right hand corner and select Export to XML. In the XML you will see something like this:…
-
This is very common, and the reason is that sprints are not project specific. Usually this happens if someone adds an issue to a sprint from within the issue details instead of using the board to drag and drop the issue into the sprint. Your only way around this is to find the issue that has the sprint used by the other…
-
No, smart values are only available in automations.
-
The approval email can be modified, but when it comes to the request type there is no variable for it. These are the available variables that can be included in the customer notification:
-
Hi @Testimony Akinkunmi, Welcome to Atlassian Community! If you are trying to share a page with people outside of Confluence without giving them access to your instance then public links is the way to do it. the other option would be to add the people as guests to your space and they would then have access to pages in that…
-
Hi @Maxime Haddad, Welcome to Atlassian Community! The Forms smart values are only for copying the data from the form and then act on it, it is not for updating the form answers. Currently the only way you can edit the answers is by manually do it in the form, it cannot be done via automaton or REST API.
-
Renaming the status will not have any affect on the history of past and current issues, the change will only affect issues going forward. The same thing applies if your for example change values in a custom select field.
-
Hi @cameron.jones, Welcome to Atlassian Community! You can do this by using issue security, once you can configured it you can make specific issues only visible to the people defined in the security scheme. For example, I use it in our HR project so onboarding/off-boarding tickets are visible for everyone that have access…
-
Hi @Grayson Price-Dairanieh, Welcome to Atlassian Community! It can be done, but it would be a scheduled automation that uses the send web request to to do it. Another option would be to use groups, and as soon as you add users to a specific group they would be assigned the JSM license and get access to the projects that…
-
You can use the other gadgets too, but in the case of the Created vs Resolved that one relies on the resolution field which is not set in a team-managed JSM project.
-
Okay, in that case you cannot use the Created vs Resolved gadget, since it relies on the resolution field. Instead what you can do is create your own chart that can then be added to the dashboard using the Service project report. Something like this: The report has series for both Created and Done.
-
Okay, because you are using the manual trigger you can only use that if you go into an issue and then click on Actions. If you want a scheduled automation that you can run without having to go to each issue it would look something like this: And the JQL used on the tigger looks like this: statusCategory = Done AND…
-
Hi @Aysun Far, Welcome to Atlassian Community! Exported rules can be imported, but you have to do it from Global automation, meaning that only Jira product admins can do this.