Brock Jolet Rising Star

Great video! Thank you for your suggestions. I had not done much with the slider field type, but it has potential. Our leadership loves visuals, so they immediately gravitated to the progress indicators for delivery progress. However, they see different visuals when logged in versus when I present a view due to the…

This is a great start. Thank you. I would still like to be able to assign permissions per view.

Please vote for this: https://jira.atlassian.com/browse/JSDCLOUD-12314

You can also follow this: https://jira.atlassian.com/browse/JSDCLOUD-12314

I would recommend opening a ticket with Atlassian so that this gets more visibility.

I have a ticket open with Atlassian, but it sounds like they're blowing me off. It would help if you also sent a request to support so that I'm not a lone voice in the sea of requests.

I feel silly, but you've helped me achieve my goal. My log wasn't showing any data because the field didn't have any data in it. The smart value was correct the whole time. Once I added some data, WebDev, it appeared in the logs. Here is what I was trying to do with that smart value. I wanted to retain the existing values…

@Darryl Lee Yes, the fields are specific to the Jira Product Discovery project they are created for instead of being instance-wide. I am having inconsistent results in Automation when trying to access these fields. Some can be selected via Issue fields condition nodes, while others need to be referenced via JQL. My use…

I'm having a similar issue when referencing custom checkbox fields created for Discovery Projects. They don't appear in the instance-wide custom fields section, so I can't find the customfield_xxxx name. When I build JQL for them, this is the correct format: * "Teams[Checkboxes]" is not EMPTY However, I can't figure out…

Thanks, John, but that doesn't help. The ProForma field captures rich text regardless of what I do. I see garbled metadata if I keep my custom fields as plain text. I can swap them to Wiki Style, but then my users are incentivized to add rich text formatting that I do not want. Unfortunately, the latter is the only viable…

@John Funk, I misread your comment. I thought you suggested enabling Wiki Style for my custom fields. As far as I know, I don't have any control over the new paragraph field type.

That is an option, but I don't want rich text. I just want the old-style plain text, multiline input.

I have a related issue: https://community.atlassian.com/t5/Jira-Service-Management/Can-no-longer-add-plain-text-multi-line-fields-in-JSM-forms/m-p/2255961#M3456 I hate how Atlassian changes stuff without warning, and we must deal with the repercussions.

Update. Their proposed solution doesn't even work. When I try to link the field it tells me I have to use the new paragraph-type field.

Once again, you've saved the day! Switching to type.name was all I needed to do. {{#issue.issuelinks}}{{#if(equals(type.name,"Hierarchy [Gantt]"))}}{{inwardIssue.key}},{{/}}{{/}}

I followed the steps in the link from Sabastian through Step 7 and was able to then add a "Field has been modified Validator" to achieve a mandatory comment without a 3rd party app.

Bill is always on top of things, but I also wish I could have a site-based template library similar to how I can create custom templates in Confluence.

Thanks!

Thanks, Bill! I'll try this out to see if it works for my situation.

Hello Jack, I think Automation is not able to pull the email address of the {{currentAssignee}}. It needs to be explicit. See my example of a working rule below:

The linked issue is for including Expand macros inside tables and has been implemented. I'm trying to use an Excerpt macro within an Expand macro or vice versa. Is there an issue I can upvote for this functionality?

@Sona Evanesyan , Thank you! This was the breadcrumb I needed.

Hello @Maksim Marholin , I name my rules so that I can quickly recognize their function. In some situations, I have many rules that do very similar things with slight variations (i.e. create a clone in a specific project). Yesterday I was taking stock of existing rules and filling in gaps. I needed to quickly reference…

Thanks @Tim Perrault !

Well, that's unfortunate. Thanks for the reply.

Hey @Bill Sheboy I'm working on something very similar to this, but I'm curious if it's not possible to store the entire list of issues to a variable (without the ".size") and then filter them later on in the rule. Example: I do a {{lookupIssues}} and add that result to a custom variable called {{xAll}}. If I ask for…

Here's the bug card: https://jira.atlassian.com/browse/JRACLOUD-78205

Thanks, @Bill Sheboy . This put me on the right path to accomplish my goal. I originally was going to do more actions in the same rule, but opted for multiple rules. So I was able to remove the IF statement and removed my JQL search from the Cron. I didn't need to store a custom variable, but I did use…

Hello @John Funk , I read through that thread and don't think it addresses my issue. I'm already producing emails with a list of issues via the Lookup Issues component. The problem is that I'm getting multiple emails with the same information instead of just one. I'm returning a list of issues from my IF statement, pulling…

Hey @Bill Sheboy Thanks for the replies. Here is the full automation as I have it today. It seems to work as intended. I find it strange that it lets me drag the "Clone Date is not empty" components into place, but not create them in place. Just another Jira quirk, I guess.