Kai Becker Community Champion

Hi Mayki, that the right way, yes. But if you would like to compare the value with an email address, I would recommend {{comment.author.emailAddress}}

Hi @Mayki Gonçalves thanks for your question. You should be able to use the issue commented trigger and interact with the {{comment}} smart value. {{comment.author}} gives you the user {{comment.author.displayName}} would give you the name to compare. {{comment.internal}} will return true or false depending on the JSM…

Hi @Nicole Cecotto Roig both apps usually offer a certain setting to remove certain parts of the mail body, like footer. This can be done via regex. Here is a documentation for example. Hope this helps.

Hi @Jim Smith That's why I wanted the JSON, to see what format it is. Glad that it has been resolved in the end!

This should already be available in your version. What is the response you are getting? I forgot to mention, that this endpoint will report all versions, not only the ones used in the fixVersion field 😕

Hi @Nicole Cecotto Roig welcome to the community and thanks for your question. Using Jiras default mail handling capabilities this is not possible. If you want to extract information from the mailbody you will need to use an app for that. Two popular examples on the marketplace would be: 1. Email this issue marketplace…

Hi @Morten Dieckmann-Keden would you mind creating a separate question, as you are using a different technique on a different plattform? You are running Jira on server/dc which has this old style integration. Emma uses cloud, where Asset automations are integrated. As a hint, I would switch JQL from trigger and condition…

Hey @Ben Radlinski thanks for your question. There is a special REST API endpoint for this: https://docs.atlassian.com/software/jira/docs/api/REST/9.10.0/#api/2/project-getProjectVersions

Hi @Alex Smith welcome to the community and thanks for your question. Actually there is an easier way than creating a variable and copy values. You can just edit the issue field in your loop an copy over the value from the trigger issue: Hope this helps 🙂

Hi @Yuliia Vyborova thank you for your response. You are right, you need to specify the variable from the previous step. You might try a different variable name, as parentLink might be something internally used. Also I would recommend to log the variable content to the audit log using Log Action. This should return an…

Hi @Jim Smith could you please post the json of an issue that has value in the PI field, as I requested? One more question: Do you update the field via advanced edit?

Thats a good one. Have been doing this quite a few times with my last team. :)

Hi @Jim Smith thanks for clarification. I'm not a hundred percent sure about the field update, as I don't have a PI Start field in my product discovery project. What I would recommend: open an issue from the project (that has the field set) via rest api: https://<your site name>.atlassian.net/rest/api/3/issue/<example key>…

That's strange. I would recommend opening up a ticket at the support and let them check this. I haven't experienced such a behaviour recently.

Hi @Janell Peyton thanks for clarification. It sure can be done, but I wanted to check the for the aspects to give the right answer :) The easiest way would be to copy the board filter and add the following JQL: AND type = "ad hoc" After saving this modified filter copy you can switch the filter on the specific board we…

Hi @Tuyen Vetter welcome to the community and thanks for your question. Do these delays occur even after a reload of the board?

Hi @Janell Peyton thanks for your question. Could you please explain a little bit more what you mean by "ad hoc ticket types" ?

Hi @Jim Smith welcome to the community and thanks for your question. I'm not a hundred percent sure about the Project Discovery fields, but I don't think it is necessary to put mediumDate after now. You should be good to go with now. Jira should sort this out internally. 

Hi @Jackie Story welcome to the community and thanks for your question. The feature you are currently looking at is pretty new. At the moment, there is only basic field support but Atlassian is constantly improving on features in JSM. Next in line of upcoming features there will be improvements in fields and also new field…

Hi @BOUKHELKHAL Sara welcome to the community and thanks for your question. There is no way using anything else as a knowledge base. Confluence is the only option. I would recommend having a look at this thread, with instructions on how to migrate the content from GetGuru to Confluence.

Thanks for your wrap up @Jimmy Seddon 🤙

Hi @Nate Dickinson thanks for your question. If i got it right, their project is now placed inside your site? So the Atlassian Cloud base url is the same? If this is the case, the executions of these global rules will count on your rule execution limit. As you are using cloud premium, you have got 1000 executions per user…

Hi @Yuliia Vyborova thanks for your question. First thing I saw in your JQL: issuekey This is not a valid JQL syntax. A single issue key would be referenced like this: key = XYZ-1 Maybe this already solves your problem? If not, it would be good to see the part, where you create the variable.

Hi @Andrew Gansler you should be able to use smart value string functions: {{issue.summary.remove("[REJECTED] ")}} The full documentation on these functions can be found here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ 

Hi @Callie Dambrisi welcome to the community and thanks for your question. You need to update the field via the advanced update function. Please have a look at the answer from Mikael in this thread

Hi @Daniel Hana you can split up screens for issue types in Create / Edit / View. You would need to split your screens and create a separate one for view and then remove the specific field. Hope this helps.

Hi @Rakesh what do you mean? What is your question?

Hi @Akash Panchal what do you mean? :) This query returns all issues with alle issue types. First column contains project name and second column the list of issue types. Forgot to mention: this is testet on postgresql database If you want to get a list for a single project, you could add a WHERE clause with the project…

Hi @Akash Panchal building up on your query, the following modification might do the trick: SELECT P.pname, STRING_AGG (DISTINCT I.pname, ',') FROM project as P INNER JOIN jiraissue J on J.PROJECT = P.ID INNER JOIN issuetype I on I.ID = J.issuetype GROUP BY P.pname; Please be sure to double check the results with a simple…

Hi @Shikha Verma did you copy the issue type scheme? You should only modify the copy of the issue type scheme. After modification of the copy, assign the copied scheme to the ID project. Are you sure, that you have done all these steps correctly?