Walter Buggenhout Community Champion

Hi @Nathael Dreymann, The part about synchronising status, automation is your best friend. With 2 automation rules, you can keep the statuses between your story and sub-tasks in sync. Both rules are available in the template library: * When a sub-task moves to in progress, do the same for the parent story * Transition…

Hi @Jeanne Schock, JSM originally used to be a plugin on top of Jira (Software), where request types were introduced as additional, user friendly forms to support portal access only. Customers should be able to create issues without having to read a manual first, so all the unnecessary fields and context for regular issue…

Hi @Orestis Vasilakopoulos and welcome to the Community! Your rule could look somewhat like this: I do not have an archived status in my demo instance, so you should obviously set the appropriate status instead. Hope this helps!

Hi @Ivan Andrieiev, Filter access settings are configured individually, so you can't update multiple filter's settings at once via the UI. Shares can be added via the cloud API, but that may be overkill for just 2 filters. Hope this helps!

Hi @Parveen Taj, First of all, you need the Structure.Gantt Marketplace app as an extension to the Structure core product. Once you have that, check out the app's user guide to learn how to create and configure the charts. Hope this helps! 

Hi @Theresa Clemmons, Yes. In view settings, select the option Lines next to dependency style: Hope this helps!

Hi @Flynn Gerald Dolino and welcome to the Community! I suppose that these statuses are coming from issues in Team Managed projects. Although these statuses have the same names, they are different, as they are configured separately and linked to their project only. If your projects were company managed, you would not face…

Hi @Jessica Huebner, Just to keep things consistent here and relating to your trigger: Just thinking maybe I have this part set up wrong. I initially had "Value deleted" but then changed it to "Any changes to the field value" but still can't get it to trigger (I have a test ticket I'm closing/reopening): This is how I set…

Hi @Jessica Huebner, An automation rule like this should let you do the trick: Leaving the value for the fix version field blank in the final Edit issue step will clear the field value. Hope this helps! 

That indeed, or updating them via bulk change or manually. Any way you look at it, you will need to fill out the values again in the new field, in the new project.

Hi @Nicholas Krall, To expose your data publicly, you would have to enable public access to not only the filters, but more importantly the projects where the issues are stored. This support article describes the configuration steps for both projects and filters/dashboards. However, be aware of what you are doing there…

About the custom fields, @Brennan Karrer - custom fields in team managed projects are set up only in those projects and not shared across Jira. The are silos, if you look at them. And, as the documentation states: you lose custom field data when you migrate to company managed projects, where you have to re-create them: *…

Hi @mike_smith and welcome to the Community! Not sure what you mean, exactly. The notification settings are defined by their project, but once they are sent out, they become separate email, slack or other messages dropping into your dedicated communication tools, where they are out of Jira. Since you can even send…

Hi @Brennan Karrer, Choosing the wrong project type and realising it too late unfortunately leads to these scenarios. I hope you have found this support article which lists: * the recommended steps to migrate * the data that is - unfortunately - lost in the process If you have some kind of way to select the issues that you…

Hi @Ilona Graca and welcome to the Community! With the exact query you shared in your question, you seem to be searching for issues that were created in 2022 and resolved in 2020. That is probably a typo. Issues get resolved after they are created, so it is quite normal that your query does not return any results. Hope…

Hi @Vanessa, Tempo is a marketplace app. Marketplace apps are billed at the same number of users of the core Jira product it is installed on. To be even more precise: if you have more than one paid Jira product (e.g. Jira Software and Jira Service Management), than the marketplace app will be billed according to the Jira…

Hi @Edward Maldonado and welcome to the Community! Depending on a single person and email notifications for managing service does not sound like a very healthy setup to me, to be honest. Maybe you are getting so little requests that it does make sense, but otherwise encouraging people to use the boards / dashboards /…

Hi @Mikel Whipple, If you do not want to track the data in a Jira field and just have separate fields on your form, then the simple workaround would be not to map any of the user fields to a Jira custom field at all. You can perfectly add multiple user picker fields to your form and they will retrieve users from your Jira…

In an emergency situation, it is quite common to open a war room (that may be a dedicated Slack channel or sometimes, when you're working co-located even a physical meeting room) where you allow people to communicate amongst each other about the issue. Bringing people together to solve a really big problem is usually a…

Hi @Alex Zager and welcome to the Community! The field and the value in it are two different things. You should be perfectly able to add a regular date picker custom field, which you then fill out via the logic in your integration. How you do so depends on how you interact with Jira. If there is any reason why you cannot…

Hi @Omril and welcome to the Community! Creating a new sub-task issue type in Jira's global configuration will only work for Company managed projects. To make it available in your projects, you will have to: * add it to the issue type scheme used in those projects; * decide what configuration the issue type will use in…

Hi @Rich Schmoeller and welcome to the Community! It is perfectly possible to add users to different organisations and multiple sites. But if you plan to set up an AD integration and SSO via Atlassian Access or claim a domain, only one organisation can "own" the accounts. That is the part you should definitely avoid doing…

Hi @Randy O'Neal, The below query in Scriptrunner enhanced search would return all issues in open Epics: issueFunction in issuesInEpics("statuscategory != Done") You can refine the part between parentheses of course to limit the list of Epics to certain projects as well. Hope this helps! 

Hi @Валентин Крыжановский and welcome to the Community! There is no way to add a screen to a delete operation. Create, Edit and View are the only operations you can associate screens to, which represent the fields that are visible to the user when they are manipulating an issue. When you have the permission to delete an…

Hi @Silvio Keller and welcome to the Community! This means that you do have project roles in your server instance, but that you don't use them for assigning permissions properly in the projects you are trying to migrate. JMCA (rightfully) does not like that. You should assign users to roles in the projects you are…

As I mentioned, without apps Jira does not offer good support to find linked issues or parent issues of a dynamic selection of other issues. If you would like to find features that are linked to a parent initiative, you could search with: IssueType = Feature and "Parent Link" is not empty If you add the column Parent Link…

Hi @Tim Waymark, I am guessing this is a screenshot from a Team-managed project. As far as I know, there is no built-in option for fix versions available, but you can create a workaround by defining custom filters for specific versions (assuming you won't be working on many versions simultaneously). From the ... button in…

Hi @LG and welcome to the Community! From your question it is not clear what Jira Software Plan you are on. What you describe seems to point in the direction of premium. And in that case, you have Advanced Roadmaps in your site to visualise the relationship (and even enable planning and roadmapping of your structures). You…

There is no setting, @Ivan Andrieiev. Dates do roll up, until you manually interfere as I explained in my previous answer. This support article explains everything there is to know with regards to the behaviour. 

Aha, now we are talking 😅 There is no setting that lets you disable this behaviour, as far as I know. It is normal that the duration of the Epic covers the aggregated start and end dates of its child issues. However, if you drag the timeline of the Epic issue to a different slot, you will see it can move freely. This can…