Vishal Biyani Expert

@Martin Flury You are most probably not using smart values in the right way. Can you share the screen shot of what you have in email form?

@efe.demirbag When you click on Teams as shown in below snip Then you should see menu option to Create Team. Once you create the team, then it will appear in Team dropdown in issues. 

@Priyanka Agrawal To make the update work from StandardIssue -> Epic -> Initiative, see below instead of using portfolioChildof need to use triggerIssue to reach the Initiative key from Standard Issue Hopefully it will work in your use case. Thanks a lot @Trudy P Claspill for your insights.

but is there a date when the deprecated APIs will stop working?

i don't think JIRA automation supports that :-( you will need to use to If or else block

This is a nice feature to be enabled

I wanted to add a label to multiple pages based on the starting letter of the page title. As there were over 100 of pages, automation helped achieve the task in minutes

In the edit issue fields parent, you need to provide a key to make the current issue child of epic. So, you can add this under more options. replace EPIC-123 with your actual value { "fields": { "parent": { "key": "EPIC-123" } } }

assuming in ${params.resourceId} you are passing your tenant id of your cloud instance, Check the response status code as well. if status code is not 200, then One of the reasons why you are not seeing the boards is either you are passing wrong credentials or the credentials that you are using doesn't have permission to…

@zohaib aslam can you share the end point that you are using along with the payload?

@Amit Tandon Another option is to copy these values in a custom field using automation. Then the custom field can be viewed in the Two-dimensional table.

@Daryl Marsh if you want to aggregate story points from Standard Issue Level to Epic, you will need to write an automation to do the rollup. JIRA does not do that out of the box. Could you list down the columns that you want to report on? Can you clarify the last column that shows % is that Progress % column provided by…

@Michael de Marigny Assuming you have defined set of epics. For the created issue (Standard Issue Type), you want to link this issue to the epic. So, within the same rule, you can add if/else condition if location matches Sydney Then add Edit Issue Condition, with following rule in { "fields": { "parent": { "key":…

@Chris Kurtenbach Could you try running the query by enclosing the status in brackets on both web and excel? project="Claims All" AND (Status="60 - Completed & Submitted for Payment" OR Status="70 - Pending Funds/Cash Call")

@Oliver Skelton Assuming you have the filter link use below in the mail body Issues can be viewed <a href= https://your-instance.atlassian.net/issues/?filter=10102>Here</a>

@Chris Kurtenbach Can u share the JQL that you are using in both web portal and excel? What is the total number of rows returned by JQL?

@Eran Sandman Trigger There are various triggers that can be used depending on the use case. For your requirement you can use either * When use Field Value changed and fill the details * When Issue Updated IF Condition To limit number of issues that the automation hits, you can add a JQL condition Then create the smart…

@Eran Sandman Looking it another way as you are interested in reading number of rows in a table. Table is represented by || for headers and | for body. For 7 column table, there will be * 2 pipes for header i.e. 14 * 8 pipes for each row Create this automation rule Set smart value variable like this: As long as your…

I am assuming you would have written the automation rule in JIRA to validate that count of rows is working correctly. Can you share your working rule, and we can go from there?

Can you share the rule that you have used? Using regular expression Lines breaks can be handled.

@Eran Sandman Few questions * Is the table having 1 column? * Does it have a header? * Can you share a sample data to better understand your scenario of multiple rows in certain cell? Table is stored in markdown syntax format. I am thinking this can be used for parsing and calculating the number of rows in the table.

@Mariam Mohamed Assuming you are looking for an idea as to how to implement the automation, you can do below * Add a custom field (or use labels) to track which issues have sent the previous day * Create a scheduled trigger and the time when you want to run it. in the same trigger add the JQL that you want to run. Add…

@lenka_salacova if you create another automation rule and use the trigger "when issue link deleted", that should help with the delinking scenario(s). You will need to rely on smart values {{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access…

@Saad Ahmad To rule out if some automation is overriding the values, can you test by importing the issue and not provide or map "Target Start" and "Target End". Let's see what happens in this case.

@Ramya Swamy You need to enclosing brackets to set operation precedence. I have added few brackets to meet your requirement of * return date based on GS Date and Planned End * if either GS Date or Planned End is populated. You will have to play around with below query adjusting the brackets and make it work based on your…

It helps in enriching the content (summary / description) and saves time.

@Hina Imtiaz Assuming, the epic that is mentioned in CSV file exists, can you share below details * Can you share the screenshot when you are importing the issues? That can possibly give clues as to what the issue could be. * Also, share your input csv file with dummy data.

@Saad Ahmad This shouldn't happen. Are you sure you are looking at Target Date and not at Created date column? if yes, can you share the snip of your imported issue with Target Date column value and the csv import file that you have used?

@Hina Imtiaz Can you check if these appear under Hide when empty section? in my Jira cloud instance i see them

@anna_charles You may need to check with your JIRA Admin. They may have added it and knowingly or unknowingly made this field mandatory.