Kai Becker Community Champion

Hi @Andrea Del Pilar Porras Rodríguez thanks for your question. I'm not quite sure what you mean by placeholder, but you can set default values for text fields via Custom Field Context This can be set via System -> Issues -> Custom fields

Also is there any update on MS Teams support?

Hi @Petr AST thanks for your question. I can confirm that searching for an issue key does not work in queues. I would recommend using the search box in the upper right corner. Entering the issue key there does take you directly to the issue. Hope this helps

Hi @Terry Pothin welcome to the community and thanks for your question. I am really sorry, but it is not possible to restore individual attribute values insight objects. If you do not have any backup/export of your assets data, then it will not be possible to restore this data.

Hi @Travis thanks for your question. I haven't had such a configuration but I guess it is working as expected. You need to keep in mind, that the approval process via Service Management is a huge benefit for approvers without Access to the issue view. They usually can only take a look at the portal view of the request. So…

Hi @Mujtaba shah for every customer notification, the people who should receive the notification can be selected. This is configured via Project settings --> Customer notifications

Hi @Veronika Dvorska thanks for your question. Did you invite the customer or did he register an account on his own? From what I can tell I guess the customer was invited and an account has been created, that needs to be registered completed by the customer. He/she then will be able to edit the first- and lastname. Hope…

Hi @Shubhi Jain I'm not sure about what you are doing, but I guess this is not properly formatted/escaped. Thats why the outer brackets get removed. I don't think you need to use an f string, as it is just plain text. Please try jira_comment = "[~{{assignee}}]"

Hi @Shubhi Jain welcome to the community and thank you for you question. The syntax you are using is for the cloud version, DC does not have a accountId, so that your problem right now. You should be able to just use: [~{{assignee}}] Hope this helps. 

Hi @Mujtaba shah does this happen to all requests of the customer, where he/she is participant? Did you check the personal preferences of the user? Customer notifications are also set to be send to "Customers involved" and not only to the reporting customer?

Hi @Tiziana Pisenti AFAIK this is not included in Cloud anymore. The best way to assign objects would be an automation rule. Regarding your second question. Assets default values can be set inside the config. When you click "Display a default object when this field appears in a customer portal" a default object will be…

Hi @Saki Okubo thanks for the clarification. I don't think you need to install anything in Slack, just connect your cloud site. Please follow the instructions here: https://support.atlassian.com/jira-service-management-cloud/docs/set-up-chat/

Hi @Saki Okubo welcome to the community and thanks for your question. Looks like there is a little bit of confusion here, so I'll try to clarify. Jira Service Management Cloud is a product for Service teams to help them with their customer support processes. Atlassian Assist can be used as an addon to even enhance the Jira…

Hi @Mikołaj Ogrzywalski thanks for your question, I really like the concept. Sadly there is no such option to create subgroups inside Portal groups. The structure is fixed and can't be modified: Project Portal --> Group --> Request Type There might be two workarounds: 1. Create single select fields that work as your…

Hi @Lars Morten Nygaard thanks for your question. Every issue has this information stored. Easiest way to access it: * Open issue via REST using https://<sitename>.atlassian.net/rest/api/3/issue/KEY-123 * search for organisation (customfield_xxxxx), probably 10002 * the id should be located in the json object Alternatively…

Hi @Mohammad Hariri welcome to the community and thank you for your question. Please try the following code and replace the parts in <> accordingly: from atlassian import Jira import json jira_url = 'https://<sitename>.atlassian.net' username = '<useraccount>' api_token = "<token>" jira = Jira(url=jira_url,…

Hi @Ksenia Abdulina thank you for your question. AFAIK there is no solution to your problem I can imagine. Assets does not allow to compare two versions, neither does Jira for Issues in terms of history. 

Hi @Bogdan welcome to the community and thank you for your question. I don't think that this is a good idea, as Jira might not always get the "first" user you think. I would recommend using a single user picker field and copy it over via default Automation functions. If you still need to use that multi user field, please…

Hi @Alex Vish welcome to the community and thank you for your question. As Nic already said, there is no way to actively manipulate the order by key. But what you could do: If you are using a Jira Software project, I would recommend switching to the backlog view and sort these bugs via dragging them up and down. After that…

Hi @Trenton Jivery welcome to the community and thanks for your question. This is actually a known bug, because of a behaviour of Jira Software generated workflows. More information can be found here: https://jira.atlassian.com/browse/JSWSERVER-11547

@Andy Gladstone you are right :)

Hi @Eddie Newman welcome to the community and thank you for your question. In terms of Docker containers I'm not the right one to help you out, but I know how to get an install file for you: Visting the following link you are able to download any version of JSM since release. Make sure to select the version matching your…

Hi @Bhagya Roy thanks for your question. Just to clear things up, both projects are Company managed? If so, are the fields that are missing on the screens? Could you further explain, what you mean by "removed"? Are the values removed from the fields?

Hi @deborah a plante I haven't done this yet, but one Server/DC Instances I would say pretty much everything is possible, but maybe requires scripting. Assets Automation could be used to trigger http requests to the REST API but this has two major problems: 1. The things you can configure within the Asset Automation Rules…

Hi @josh.luttrell did you see any errors in the browser console or the network tab? Does this issue persist for a few days/weeks?

Hi @Joe Serrao as of now, only slack is supported for the Virtual Agent. Connecting MS Teams is currently "Gathering interest". There is no ETA on release: https://jira.atlassian.com/browse/JSDCLOUD-12279 Do you have a link to the documentation you mentioned?

Hi @shseo thanks for your question and welcome to the community. Today, there has been an active incident targeting all Jira projects, but all products are running again. Most up to date information always can be found here: https://status.atlassian.com/

@Mirela Todorova in addition to Tansus answer I would highly recommend to practise. Get yourself a cloud demo environment and play around with schemes, fields and everything around project setup. My opinion: knowledge and practise will make you a good Jira Admin, regardless of the courses and or certificates you own 🙂

Hi @Josh Cabrera welcome to the community and thanks for your question. To better understand your problem and the rule, could you please post a screenshot of the rule and the attributes of the object?

Hi @Janice , is there any update on this? I guess this is not an easy task :(