Walter Buggenhout Community Champion

Hi @barry.guo and welcome to the Community! Product discovery is a separate product, under the hood based on a team-managed project configuration. Team-managed projects - unlike company managed - are siloed and don't share their configuration with other projects. Hope that clarifies!

Hi @Archana, No, the panel is not configurable. As per this announcement, Atlassian is working on an update that will allow you to apply flexible naming to epics themselves. You can track the status of development via the cloud roadmap. However, that change does not include additional configuration options of the contents…

Hi @Pascal Masson and welcome to the Community! First of all check all prerequisites of the pre-migration checklist and reach out to Atlassian migration support directly if you need further assistance. For more details, see your related question on this topic. Hope this helps!

Hi @Pascal Masson and welcome to the Community! As you mention you are migrating an old server version, I would recommend you to first and foremost check all the steps in this ore-migration checklist to ensure that you are on a supported version and that no prerequisites are missing. Then, for technical support, reach out…

Hi @Sura Al-Jailawi, It's a bit difficult to assess just based on your description, but the first thing I would check is whether the releases you are referring to are actually in your plan. It is not necessarily because you see them in Jira on the issue details that the releases themselves are also imported into Advanced…

Hi @Lukasz, The blue and grey colors you refer to are the status categories in Jira. Maybe also on a somewhat higher level, you could reduce every imaginable piece of work as a process that can be reduced to 3 generic steps: * to do (grey): means it has been added to your list of work that needs to be done, but other than…

Silly as it may seem, we already have several customers using JSM for customer service but heavily promote the email channel (despite of all the downsides it brings) just because their customers need to otherwise go through the steps to create an account on the portal to unlock the full potential there. For which - if they…

I did not refer to multiple records for the same person really @Alex Zhitnitsky, but that is a very valid point of interest as well. I was just thinking about the real life scenario where customers are in the field, trying to access your customer service portal. Not rarely, this happens when they have a real and - for them…

Hi @Michael diLorenzo, While there isn't really a way to use the due date in the configuration of your SLA timers, there is also no need to fire an automation rule every hour to cover your use case. Since a due date does not contain a time component, firing your automation rule once a day should be largely sufficient to…

It is not a bug, @Mike Landers, it is the way a scrum board and the scheduling of sprints works. See my answer for more details. 

Hi @Mike Landers and welcome to the Community! Yes, you need to map the backlog status to the first column of your board. If you don't, your issues won't appear in the backlog of your board - as the message says. Issues in the backlog will not appear on the active sprint unless you specifically put them in a sprint.…

👍

Hi @CT and welcome to the Community! If the field is required in just one or some transitions in your workflow, that usually because there is a workflow validator (in company managed projects) or a workflow rule (in team managed projects) enforcing the behaviour on that specific transition. In that case, go to project…

Hi @jeroen_wilmes, Yes, that is the case. As an example, suppose you currently have 2 issue types called first floor and second floor, second floor being the parent of first floor in your hierarchy. You will have the Parent field filled on on issues of the first floor issue type and you can choose from issues of the second…

Hi @David Pleşu, No marketplace apps needed. Just create a saved filter that returns the list of issues you are interested in receiving status updates for (from Filters > Advanced issue search). Once you saved the filter, select details next to the filter name and create a filter subscription. You can set a schedule there…

Hi @Anna Ehn and welcome to the Community! The timeline bars are just a visual representation of the period between a given start en end date for your issues. In your advanced roadmaps plan, you can configure which fields to use as start and end date. Check the issues in your project to find out what fields are being used…

Hi @Núria Rull Bassols, This should be the Team field. Check out this support article for more details. Hope this helps! 

Hi @Daniel Lim and welcome to the Community! Your questions suggests that you are using company managed projects. That is a prerequisite if you want to associate screens you build separately with issue types in your project. If that is correct, you need to associate your screens with your sub-task issue types through the…

Hi @Romani Rupasinghe, I had pasted a link to potential candidates in my initial answer, but I notice I must have messed up there somehow. This should be a good starting point to further investigate what might be a good fit with your needs. 

Haha, I thought your were, as I saw the long list of components in your screenshot 😉 The filter function is at its best (and is designed for scenarios) when you want to actively select just a few options, not really exclude one or two from a long list. So there's not really an option to support your laziness in the best…

Hi @Cathy Grohman, Actually, don't select anything at all. That's exactly the same as selecting all options. Hope this helps! 

Hi @Romani Rupasinghe and welcome to the Community! That is correct. Jira Software is a tool that primarily supports teams working on software projects using agile methodologies. The focus is primarily on: * delivering value to the customer of your product; * making your teams' work transparent; * delivering insights on…

Hi @Denton, Robert and welcome to the Community! The program board you refer to dates back to Portfolio for Jira 2.x (also called live plans). That view has never been upgraded to the new experience of Advanced Roadmaps and was never implemented in cloud. To - more or less - simulate the behaviour, you could set up a…

Hi @Lisa Robinson, No, unfortunately the calendar view is only available in Jira Work Management (Business projects) and Jira Service Management has a change calendar. There is a feature request for Jira Software that you can track here: JSWCLOUD-23094. Or you could search for extensions in the Atlassian Marketplace in the…

From your user profile avatar, select Open quickstart. At the bottom, there is a Give feedback link:

Hi @Laetitia Coja, From your description, it seems as if you're using a team-managed project (you can check near the bottom-left corner of your screen when you're looking at your kanban board). If so, grouping by release is - unfortunately - not possible. At best, you can add custom filters to your board that will allow…

Hi @Damien Desrousseaux and welcome to the Community! This feature was released very recently (see cloud release notes May 8 to 15) and probably still rolling out to sites. I don't see it in my test instance yet, e.g. I suppose that the smart values for automation as a result simply aren't available yet. You may want to…

Hi @JD Lobue and welcome to the Community! You cannot disable the navigation bar in Jira Cloud. It is the map for anyone with a license to the product to find their way around in the product. However, all the items can be restricted: * In the list of projects, a user will only be able to see the list of projects he/see has…

Hi @Özge Özgenç, You seem to have figured out quite a big piece of the puzzle. It is perfectly possible to add 2 edit issue actions to the same rule, one to create the first link (the one that you explicitly set) and another to copy the links from the original issue: Hope this helps!

My doubts are linked to the idea of automating the creation of a blocked issue (responding to the issue created event means you either have to build in a lot of conditions to avoid ending up with lots and lots of blocked issues you may not even need). I would consider rather using e.g. the issue linked trigger instead.…