Walter Buggenhout Community Champion

Hi @Christopher McKenzie, It seems you are trying to manually create what Atlassian has built into Atlas. Since weekly updates after a full quarter ends up to be a lot of text, it does not present nicely on a dashboard, even if you would succeed in making it work. Have a look at more details over here. It comes with a free…

Hi @venkatesh bojja, The unfortunate answer is you can't. Separate quick filters are always combined with an and operator if you activate multiple of them on your board. Hope this clarifies! 

Hi @Steve_G, No. Dependencies are issue links between Jira issues. They are not something that can be inferred or rolled up. They need to be physically created between issues in order to display them as a dependency line in the roadmap. Hope this clarifies! 

Hi @Zach Detwiler and welcome to the Community! What you are asking about is what essentially any organisation that uses Jira as a corporate application should be doing: have some governance in place when necessary, manage the configuration so it scales and creates some sort of familiarity across projects, teams and users.…

Hi @Geraldine Benitez and welcome to the Community! Both of these are not standard issue types in Jira. You can create your own issue types and upload any icon you like for it. So, feel free to be cteative 🔥🛠️🎁 Hope this helps!

Hi @Ravuri, SuryaBhagavan (Contractor), Have a look at this series of support articles on sandboxes. They should have all the information you need. Hope this helps! 

Hi @Manu and welcome to the Community! To a certain extent, yes. You can search for issues on the summary field, but it will always be an approximative search, like this: summary ~ "some text" Because the field is free text, you can not use it to group reports by it. You should see that the options you have will always…

Hi @Alper Saglam _actioner_, This is a team managed project. The sprint report does not exist there in exactly the same way as it exists in the scrum board you know from company managed projects. If you look at the Sprint Burndown Chart, you will see that most of the information is there in a single report. Hope this…

We'll need more details on your setup, @Nick Turner - but based on what you describe, the most likely reason why the last step fails is that request types are linked to issue types in Jira Service Management. If you are trying to set a request type that is not available for the issue type you have just created, then this…

Hi @Santhosh Raj, See this support article to learn more about attachment limits. In short: on a standard plan the default maximum size for a single file is 1 GB. The total storage capacity of your standard JSM plan is 250 GB. Hope this helps! 

Hi @Eva Maria Valero, Not if your project is team managed. In those projects, you are confined to the predefined options to group by: assignee, epic or subtask. In a company managed project's board, you can define swimlanes to achieve the same result. While you cannot just select the custom field you have set up…

Hi @Juan José Balcázar Fernández and welcome to the Community! A collaborator in JSM is a member of the Service Desk Team role that does not have an agent license. As long as you have users with a valid license to another Jira product (e.g. Jira Software), they will get limited permissions to your JSM project if you add…

Hi @Kranthi Kumar, You are correct. In JSM there is only 1 board for a project. If you want to set up multiple boards for a project or a single board to pull in issues across multiple projects, you would need to start from a Jira Software company managed project. Hope this helps!

Hi @Rohit Mhalsekar and welcome to the Community! You may want to take a look at this Community article on searching for an exact phrase in JQL. Hope this helps! 

That depends if the workflow this status is in is company managed or team managed. If it is company managed, you will most likely need to create a copy of the existing workflow and then, editing that copy (assuming you want to replace open with new): * Add the existing New status to the workflow * Make sure the New status…

Hi @Kamil Askerov, The error occurs when the rule tries to transition an issues to a status that is not available for that issue. Your rule wants to execute the same transition your trigger issue went through - for all issues linked to that issue. If there is an issue in a different status or an issue in a different…

Hi @Maria Savignano and welcome to the Community! What does your board filter look like? Is it pulling in issues from multiple projects and - if so - how does it do that? In the past, I've seen several cases where the board filter was "complex", meaning Jira cannot determine for sure what the scope of projects included in…

Hi @integrity-jira-user, I'm afraid not. An issuetype in a project can only have a single active workflow. If you remove statuses that issues currently are in, they must be remapped to (a) new status. Otherwise they would end up in an inconsistent state. But Jira just won't let you. Hope this clarifies! 

Hi @integrity-jira-user, Since you set the resolution on a workflow transition, you can use workflow properties on that specific transition to show / hide resolutions as you want. Check the section on transition properties in this support article on how to configure this. Obviously, you will need to make sure your epics…

Hi @Troels Møller Larsen and welcome to the Community! No, this is not possible with team managed projects. Epics and their child issues need to be in the same project. If you use company managed projects instead, this is perfectly possible, although the Epic Link field has been replaced by parent instead. Hope this helps!

Hi @Jira and welcome to the Community! It doesn't seem as if this is a recent change. However, there's a related feature request that has more context that you can track here: JRACLOUD-70206 Hope this helps!

Hi @Riley Hosking and welcome to the Community! I cannot think of anything that might be wrong. When you configure an SLA, you set a couple of things: * triggers to start and stop your SLA timer * criteria to determine the target times to answer or resolve your tickets (e.g. high priority tickets should be answered within…

Hi @Kim Killen , The problem is your query is excluding epics. You've also made it so complex to read that you probably can't untangle it anymore. You would need to get to a point where you would have something like this: Project = "Booth Sales" AND (issuekey = BOOTHSALES-1471 OR (issuetype in standardIssueTypes() AND…

No, the screenshot you included is - am I guessing - just coming from Atlassian's public Jira Software instance. What you see there are the built-in vote and watch features of a Jira (Software) ticket. But since Atlassian builds the product themselves, they don't have to worry about the licensing cost of such an approach.…

Hi @marianna_taborda, You might want to take a look at Jira Product Discovery. That could be exactly the thing you are looking for. Hope this helps! 

Hi @Sabrina Kelley and welcome to the Community! I notice that your status "transaction posted" is a Done status. It is green and it is the rightmost status on your board. Issues that have reached this column are hidden from the board automatically after 2 weeks. That probably explains the difference. And it is also a good…

Hi @Sachin Guttala, Can you explain how your customers are seeing the SLA? Unless something changed recently, SLA information can only be shown to customers via marketplace apps or if they have internal access to service desk tickets. See this open feature request: JSDCLOUD-325

Hi @leigh.robbins and welcome to the Community! You could come close to this by adding a two dimensional issue statistics gadget to a dashboard and use labels and status (or resolution) as the axes for the gadget. Although I would rather create a specific custom field Theme to represent your themes instead of using labels.…

Hi @John Lord, I noticed this question has not been addressed; you are addressing the most complex and layered part of configuring Jira projects. Let me give it a try ... Yes, you should be able to make this work. In a company managed project, every available issue type can use its own screens. But you need quite a few…

Hi @Karpaga Selvan, You should be able to just upgrade your plan to standard, which automatically starts a trial period. Just navigate to admin.atlassian.com and select Products > Manage Subscriptions. Change your plan for JSM from free to standard. Hop this helps!