Walter Buggenhout Community Champion

In cloud, navigate to Filters > Advanced issue search. Then search for the issues you want to move. In the top right corner of your screen, click on the ... button: Bulk change should be there. If it isn't, that would mean you don't have the necessary permission.

Hi @Samir Moubarak and welcome to the Community! The simple answer is: you can't. A bit more context: issue types are a crucial part in the configuration of your project and Jira in general. When you create an issue, the issue type determines what workflow the issue will go through, what custom fields are displayed on…

Hi @Suyash Rane , To fix the error, just update your filter to the following: project = PRISAAS AND type in (Epic, Bug) ORDER BY Rank ASC I can imagine you will still need to figure out how you want to relate bugs to epics to then build a sensible roadmap afterwards, but I expect this should eliminate the error. Hope this…

Hi @Shaun Mahoney, Changing the status of multiple issues this way implies you are able to drag and drop them all to a column or status you can see in the same view. You cannot drop them into a column that is not on your screen (e.g. if your backlog is a separate view) or if the configuration of your project's workflow…

Hi @Charles Owen and welcome to the Community! Could you be more precise about what screen you are referring to in your question? Reading between the lines, my best guess is you are referring to a board where you move a card into the done column. As the issue you just move to the Done column, it gets focus and you indeed…

Hi @Mayra Bührer, No. A task cannot be displayed unless it is actually there. If you know that you are going to schedule these tasks every week, you could consider creating them longer in advance (e.g. create all tasks for the coming 4 weeks instead of just one week). That would allow you to see them on the calendar for a…

Hi @Amos Fletcher After you have added the row to your page, select some text in your new table row and you will see a small pop-up dialog appear: Click Create issue. A new dialog will show up that lets you specify the essential fields to transfer to the new Jira issue: Note how only summary and description can be filled…

Hi @Geo Mukkath, Yes, that is correct. That is how Jira Software works. The underlying principle is that you should estimate stories or tasks as an item of value that you will deliver as a whole. Sub-tasks help break down the actual implementation of the work, but are not intended for estimating. You may want to check out…

Hi @Chris Rollins, Unfortunately not. Dashboards (and available gadgets) are designed to be used agnostic of projects. Many gadgets can be based on saved filters that span multiple projects and - as such - offer the flexibility to use most fields available in your instance. As it seems from your screenshot, several…

Hi @Tony Parsons, Try updating your link issue action to most recently created issue instead of trigger issue. Hope this helps! 

Hi @Vishnu Vardhan Chenna, Just to make sure: you indicated you are on a premium plan on your question here. If that is true, you have 1,000 global rule executions per month x the number of users you have (i.e. if you have 200 users, that would grant you 200,000 (global) rule executions per month. That's really a lot, just…

Indeed, @Suresh.

Hi @Mayra Bührer and welcome to the Community! Tasks are displayed on the calendar view based on their due date. So yes, you can make your automated tasks appear on two conditions: * they must exist (i.e. they can only be displayed after your automation created them in your project); * you fill out the correct due date…

Hi @Vishnu Vardhan Chenna, Since you seem to be on a premium plan, why don't you configure them as global automation rules? At worst, you would need to update the scope to of your rules to include additional projects upon creation, but you might even use project categories combined with JQL conditions in your automation…

Hi @Geetanjali Sharma, (Many) marketplace apps are developed by third party vendors in the Atlassian ecosystem. While the ability for marketplace partners to start applying theming to their apps was announced around the end of March, 2023 (see this developer community post), it does take time to implement these changes…

Hi @Ronhit Neema and welcome to the Community! For everything related to security, privacy and compliance, Atlassian has a very extensive Trust Center available, where you can read up on everything there is to now. You can find it here: https://www.atlassian.com/trust. There are separate sections on security, reliability,…

Hi @Chris Miller, There are - unfortunately - other and bigger blockers to the idea you raise here. The ability to vote on issues as a service desk customer from the customer portal is not supported. There is a feature request that you can track here: JSDCLOUD-1743. To be honest, I would not expect that to be resolved any…

Hi @Zineb Alami and welcome to the Community! The review changes feature is very intentional. The main goal of Advanced Roadmaps is to facilitate your planning process: move things around, see what is the best way to organise capacity of your team across multiple issues at once and then commit your plan when you are…

Hi @Robert Johnson and welcome to the Community! Currently this is not possible (yet) as setting up SSO (via Atlassian Access) requires you to claim the domain first, which is - obviously - something you cannot do for domains your organisation does not own. However, this is an area Atlassian is working to improve. An…

Hi @Tanya Fraser, Great to see you share a lot of information, but a couple of things are a bit shady, still. So I'll try to explain the steps to build a hierarchy bottom up. Jira by itself already has a default issue hierarchy that you cannot modify. It consists of Epic > Story > Sub-task. You can add additional issue…

Hi @Suresh, no. They are workflow properties. But the workaround is fairly simple: copy your workflow and make separate versions for each issue type. Then you can specify the properties you like in each workflow separately. Hope this helps!

Hi @Ahmed Daoud, In Jira cloud, when you right-click on a card on a board, you get the option to just add flag to the issue (card): The card is displayed with a yellow background colour on the board and with a small icon of a red flag. In the issue detail view, that same flag is displayed next to the status dropdown: To…

Hi @Alicia Morgan and welcome to the Community! There's no straightforward answer to that, I am afraid. It is possible to fetch a list of issues that were completed during a sprint, but it is not so dynamic that it automatically applies to any given sprint. Let's assume your sprint is called Koala (in JQL this will…

Hi @Barb Newkirk and welcome to the Community! Yes, of course. You can do so in several ways, however, depending on the type of project you are in and how this fits into your process. Since you indicate being on a premium plan and are asking about target start and end dates, I assume you are using company managed projects.…

Hi @Kaouther BEN KHEMIS and welcome to the Community! Jira software supports 2 types of projects: team and company managed. You can check out this support article to learn more about the differences. In short, company managed projects share their configuration, while team managed projects are more siloed. Advanced roadmaps…

Hi @Qais Alkhatib, The report is based on an integration with your CI/CD tools and there's a couple of things involved before you would see the data you're looking for: * a working connection to your CI/CD tools must be set up * you need to have enough production data in place and they need to meet certain criteria…

Hi @Someshwaran and welcome to the Community! It is possible that I don't understand you correctly. So to make sure: from what I understand, as soon as a ticket gets created, automation adds a comment to the ticket that is only visible internally and at that point, you would like the first response SLA timer to stop (it is…

Hi @Mahesh Kumar CD, To both questions, the answer is - unfortunately - no. The schedule's bars can be coloured based on: * component * issue type * label * priority * project * status * team * supported custom fields you add But apart from the colouring options, there is not much you can do. The closest you can come to…

Hi @muralitharan and welcome to the Community! Everything you need to know about setting up a sandbox from your environment can be found in this support article. It explains the prerequisites, the steps to create your sandbox and how to copy data from production into it. Hope this helps! 

Hi @Adam Wilson and welcome to the Community! I am seeing the same behaviour in my environment. It seems like normal behaviour. Although a bit annoying, I can imagine why this is happening: custom fields have a context defined to determine the visibility and available options (for select lists e.g.) that needs a reference…