Kelly Arrey Expert

@berecom a couple of questions will help us to help you. * Are you using a company-managed project or team-managed project? You can see this at the bottom of the left nav bar on the project page * If company-managed, can you share the query for your board filter? (If team-managed, I'm out, but I'm sure someone else can…

Hi @Yatin Shingala, don't ask me how I know this. * Save this as a filter - let's call it "has blocked by link": issueLinkType = "Blocked by" * Write the following filter which calls the above filter: status = Blocked AND (filter != "has blocked by link" OR issueLinkType is EMPTY) See JRACLOUD-73640 for more info.

Hi @Tamar Peer We use the Ugubi Threaded Comments app mentioned above. It works pretty well.

The People tab is the place where project admins assign people and/or groups to roles for that project, in contrast to the global default roles set at the system admin level.

Hi @Sebastian Braun @Trudy P Claspill , I haven't tried it myself, but would {{createdIssue.key}} do it? The documentation seems to state that it would work. HTH, Kel

Hi @Ivan Andrieiev, which parts are unclear? Are you working in a company-managed project or a team-managed project. Do you have Jira admin permissions or does someone else do your Jira administration?

Hi @Minakshi Sharma, We use Structure by Tempo to implement a deeper hierarchy. We find that Structure is more flexible than Advanced Roadmaps. There's more information about how we did it in this article and this webinar. I'm not affiliated with Structure by Tempo, I'm just a happy customer. HTH, Kel

@Barbara Shaw Apologies Barbara for being late to the party but the documentation you're referring to is about adding restrictions of what Resolution values will be available on a particular transition. The more general question of how to add a new value to the list of Resolution values is described here, and it's not…

Thanks for the update. Very glad to see that independent scrolling has been implemented so quickly!

@ERRAJI Hamza For example, you could define Components for Test and Docs, and use the Component field to filter Test and Docs tickets, or similarly use the Labels field, or define a new field. However, if you need different workflows for Test and Docs, then you would need to have different issue types.l

Hi @Gavin, It looks like you've found yourself a Jira bug! The docs say that: resolved = "2023-04-13" is valid JQL, and the JQL syntax checker agrees. But it fails to return any of the hits returned by your query: project = MDC AND resolved > "2023-04-12" AND resolved < "2023-04-14"

Hi @Ifat Keren, We use Structure by Tempo to implement a hierarchy above Epics. Here are links to an article and a webinar explaining how we did it in some detail. Disclaimer: I have no affiliation with Structure by Tempo except as a happy customer. 

Hi @rbalamu2, Here are the docs: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.versions-- HTH, Kel

I know what you mean @Trudy P Claspill, I wish all that documentation was on a single page so you could search it once instead of having to search each page individually.

See also https://community.atlassian.com/t5/Automation-articles/New-Automation-action-Create-lookup-table/ba-p/2311333

Hi @Trudy P Claspill would `issueLinkType = "is blocked by"` work in this context? Here's the doc: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/#Issue-link-type

My approach would be to make the automation rule append a comment that @mentions the assignee, and then let them add a new comment, but that's just me.

Hi @Mimi Peters Sorry, I was thinking laterally. If you toggle from Basic to JQL at the top right of your Issues page, you could add that JQL snippet to your query and see all the issues reported by that unit. You could save a different filter for each unit. This wouldn't require a label or an automation rule (but you…

One approach would be to create Jira groups which list the members of each group. Then you could write JQL like: `reporter in membersOf("Unit A")`

Hi @Tom Rufo You might want to have a look at the "Hide when empty" section under Configure the issue layout.

I never knew this. Good to know! Thanks @Jared Kells 

The closest thing that works today might be to send a Slack message (or some other kind of message):

Hi @Suseendran Rajkumar Please see Configure the Issue Layout. HTH, Kel

Hi @Angela, another approach is to set up a workflow that has a very restrictive validator on the Create transition, so that no one can create issues, and then assign that workflow to the Email Deployment issue type in the Workflow Scheme for the project. That way the existing tickets will live on, but no new tickets can…

The Structure by Tempo add-on can display the rolled-up values in a column in the Structure view (although it doesn't store the rolled-up value in the parent issue, at least not yet). We're happy Structure customers who have used it very successfully for several years and recommend it very highly. 

A couple of things come to mind: * Check the Board for:* a Quick Filter that could be hiding the issues * a collapsed Swimlane that could be hiding the issues * Check the Board Settings page for:* General Tab:* Check the board filter * Check if there's a sub-filter * Check if there's a "Hide completed issues older than"…

@David Pleşu If you're a Jira admin or project admin, you should see the "Configure" button at the bottom of the right sidebar in your issue detail view, that's how you configure the layout for the issue type. See https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-layout/ 

It sounds like DAP Reason 1 and DAP Reason 2 are set up as a single "Select List (cascading)" field, as opposed to two separate Select List fields.

Hi @Leon Kotovich, as @Mark Segall has mentioned, there a several ways to accomplish this. My recommendation is Structure by Tempo. I have no association with Tempo, I'm just a happy customer. Here are a couple of links which give some details on how we've implemented a deeper issue hierarchy with Structure: * article *…

Hi @Alison Milne, There are two approaches: * You can use the /excel macro to display an attached Excel file - I haven't worked with that * You can use the /link macro to embed an Excel file which is stored in SharePoint* When you click on the link in edit mode, you'll probably see the options of displaying the link as: *…