Walter Buggenhout Community Champion

Hi @Stephanie Groot, I did a test export and the issue key is effectively in the export. It is not where your would expect it though - I found it in column U of the exported result (so in 21st place in the file). I hope you can find it somewhere deep into the data pile as well 😅 Hope this helps! 

Hi @Krishna Raghavarapu, That should be possible with an automation somewhat like this: Hope this helps! 

Hi @Stephan Lieb, Anyone with project administrator permissions in a project can add (existing) users to that project. That user does need any additional permissions outside of the project. Most commonly, that would be your project manager or lead of the project. Hope this helps! 

Alright, @Mesrop Yaghubian - understood 🤗 That is how I am working right now. My wish was to bring down the number of results to keep a better overview by "hiding" sub-tasks of my stories. But if this is not possible I have to work with my whole bunch of work items in one view :-) Here's a list of marketplace apps that may…

Hi @Mesrop Yaghubian, The following should return all the issues that you need: Issuetype in (Story, Sub-Task) AND Assignee = currentUser() AND Resolution = Unresolved If your plan is to get a list of issues assigned to you, then I would not over-complicate things by adding additional parameters from stories assigned to…

Hi @Shari Fitz-Patrick, Resolution does not impact Jira's understanding of complete/incomplete when it comes to closing sprints. On a scrum board, issues are considered completed if they are in the rightmost column of the board. If you have any issues (sub-tasks) sitting in a different column on the board, those are the…

Hi @Julien Stockerl and welcome to the Community! I assume your Jira project is team managed, while the other one is from a company managed project. A team managed project does not allow you to set up multiple boards. You can either toggle on or off sprints and the backlog features, which essentially makes you influence…

Since you are on a premium plan, I would reach out to Atlassian support to diagnose if this is a glitch on your site. You can do so via https://support.atlassian.com/contact/

Hi @Joemar Tactay, Currently not, as far as I know. If you notice something that was not entirely correct after you created a ticket, the current practice is to quickly report that as a comment on the original ticket. Communication is the main focus on handling tickets in JSM between parties involved. As a potential…

Hi @SHEHZADALI ISMAILY, Assuming that you want to keep an eye on data completeness/consistency of the issues that are being added to your sprints, I would suggest an alternative approach to automation. As you basically want a list of issues that do not match the criteria, you could set up a JQL filter like this: Project =…

Hi @Monica P_ Sykora and welcome to the Community! The second card being humor definitely leaves you wondering, doesn't it 😉. Great observation - passed it on the Team Playbook team. The playbook is an awesome resource, packed with tons of useful knowledge and fun to use by the way it is documented and designed. That does…

Hi @Nicholas Ren, Unfortunately, it is not. That basic roadmap is only capable to display the built-in issue hierarchy of Jira, which has 3 levels: Epic -> Standard Issue Types (task, story, bug, ...) -> -> Sub-tak Issue Types (sub-task) The Project you created is a standard issue type, so it will be displayed at the level…

Hi @Maksym Ivanchenko, This seems to be a known issue (for quite some time), reported in JSWCLOUD-22570 with respect to automation rules, but extending beyond that scope as well. There does not seem to be a workaround. The good news is the ticket status is in progress, but at the same time it also seems to be unassigned.…

Hi @Durga Prasad and welcome to the Community! That is not really how it works. You connect a Confluence space to your JSM project in project settings and then the KB in Confluence is constantly searched whenever a user enters text in the search or summary fields in the JSM portal, trying to avoid the creation of tickets…

You could create an automation rule for that: when the status of an issue changes status (like in the below example), then send an email to ...

Hi @Stefan Wienströer, In company managed projects, you could add a Condition to your workflow transition that does not allow to transition as long as the Sprint field is not filled out. At the same time, that is very restrictive and may lead to a configuration that becomes difficult to manage at scale. So I would also…

Hi @Tom Owens, Since you've discovered the capabilities of Scriptrunner enhanced querying capabilities already, let me focus on alternatives here ... If you are on a premium plan, you should be able to visualise the dependencies between issues via the dependencies report. It would work at its best if all the data you need…

Hi @Hiti Verma, The feature to schedule child issues from epics on the roadmap has fairly recently been rolled out and is not enabled by default. For kanban teams, the feature should work as described in this community article. How to properly enable the feature is described in this support article and you can read more…

Hi @johnb, My best guess would be that this is a permissions issue (check the permission settings of both your plan and global configuration of Advanced Roadmaps permissions). Hope this helps!

Hi @ICMS _ JIRA and welcome to the Community! No, there is not such a setting. However, in the configuration of your automation rules you can specify the list of projects the rule would apply to. Admittedly, you would need to manage/update your automation rule potentially when you add new projects, but it would be…

Hi @Nelson Steve Liteno, It looks as if the same happened to your question over here 😅 ... Most likely, the screen configuration of your projects is not identical. Maybe certain fields that are on the screens in your IT Backlog project are not available in the IT Secure project. In that case, you will not see them…

Hi @Pradeep Nene, yes of course. There is a difference between access to your site (the authentication part that you've already covered) and access to product features, such as access to a project. Every Jira project has its own, separate permissions. If your projects are company managed, then granting a user browse…

Hi @Swapnil_Tandle, No, there isn't. Session timeout can be configured from your site's authentication policies, but only when a number of prerequisites are met: * you must be the organization admin for your site * you must have verified your domain(s) * the authentication policies apply to the verified domain(s) You can…

Hi @Peter Grainger, Updating your SLA's does reflect on all tickets that still had their SLA timer running. That means both existing and new tickets. Your SLA timer - behind the scenes - has 3 potential states: running, paused and completed. Issues with a completed SLA will not be impacted by the update (as they were…

Hi @Pradeep Nene, From my own experience as an Atlassian consultant: both scenarios occur and are technically supported. I see both customer instances where dedicated accounts are created in the internal directory (Okta, Azure AD, ...) for the time being. In other instances I am accessing with an Atlassian ID not listed in…

Hi @Jimmy Seddon, happy to sign up for January 20th, if still available! 

Ah, fall! It is my favourite season for several reasons: my birthday is on October 10th, I got married on the 12th of the same month and so there's plenty of reason to celebrate a milestone here and there 🤗. Over the years, my wife and I have developed the tradition to go out on a weekend trip to the woods in the Ardennes,…

Hi @Greg Stacey and welcome to the Community, As long as your documents or files can be accessed through a url and there's no permission restrictions blocking access to the file, you can create links based on the item's url. However, linking local files directly from within Jira is not supported - mainly because modern…

Hi @Shivaprasad Hattaraki and welcome to the Community! Have a look at this related question. It pretty much covers your use case, I believe. Hope this helps! 

Hi @Tim Foster, The roadmap in a standard Jira project is graphically appealing, but is pretty basic in functionality as you elaborately illustrated in your description. In terms of tools, there are several options available to extend that basic functionality: Advanced Roadmaps in the premium plan goes a long way beyond…