Walter Buggenhout Community Champion

Hi @Mylena de Souza Nascimento and welcome to the Community! I would like to recommend you this blog post on becoming a Jira Search Ninja. It has a lot of examples on how you can perform history searches in Jira and I guess you will be able to find an answer to what you are trying to achieve there (and more). If I…

Hi @Stefano D_Angelo and welcome to the Community! Have you tried replacing the double quotes in your lastcomment() or lastupdated() sections with single quotes? project = PRJ1 AND status = "Passed to Dev" AND issuetype in (Bug, Incident, Problem, Task) AND issueFunction in linkedIssuesOf("issueFunction in…

Hi @Victor Crespo, As you haven't listed the hosting type of your Jira instance, there may be some additional things you'll have to verify for my reply to work for your case. However, out of the box, Jira does not support this type of requests very well. Searching for conditions on related or linked issues usually requires…

Hi @Ashraf B , Browse project is a permission that you set for every single project in your Jira instance. If you have multiple projects in Jira, then you manage access for each project separately. But again: if your project permissions are well defined, people will only be able to view the issues from the projects they…

Hi @Michael Woong, Your queue is based on a filter that you created. If you apply that same filter in Filter > Advanced issue search, you do have the ability to export the issues from there. You can even save the filter there, so it becomes reusable for monthly exports. Hope this helps! 

Hi @Ashraf B, There is no control over access to that menu option. There are a couple of things that indirectly impact what users can/can't see, however: * The filters > search functionality is only available to users with a Jira license. JSM Customers - who can only access tickets through the customer portal - won't have…

Hi @Glen Christensen, I suppose you want to filter for multiple users, rather than sort? You are probably running into the problem that quick filters are always combining with an AND relationship. If you have certain groups of users that you know you would like to combine in a search (e.g. because they form a (sub-)team),…

Ok, but you will still be facing the same issue you started with. There is no transition from Ready for Deployment to Closed. And as long as you don't add that one, you will still get the same error from your automation rule as before.

Indeed. 😊

I would even dare to leave out Approved all together, move directly from Waiting for approval -> Ready for Deploy (as a consequence of the approval action by the customer). And then indeed, as you say, automatically transition to closed if your custom field is not 'Yes'. That is of course based on what you are telling me.…

Hi @Clement, That would be possible if you add the manager and his/her team members to the same Organization. It is possible to share tickets being created with the organization of the reporter, which then makes it possible for people to see tickets which are shared with their organisation: For more information on…

Yes, certainly. First of all you'll need to make sure that you have transitions in your workflow for every path you want your issue to follow. Your approval step is now on the transition from Waiting for Approval to Closed. If your most common scenario is to transition to Ready for Deployment, then make sure you add your…

Hi @Meytal BM, The trigger of your automation rule says that your issue must have been transitioned to status Done. Based on your description, my guess is that you don't have a transition from Done to Ready for Deployment in the workflow of your issues. Hope this helps! 

Hi @asd asd , You can read about Atlassian's policies on security advisory notification in the trust center on the Atlassian website. Hope this helps! 

Hi @julio valdez , If you are talking about queues, that looks very much like you are using Jira Service Management - which would make perfect sense. I'll continue on that assumption and would recommend you to set up a Dispatch Time SLA, where you would start the timer when an issue gets created and stop it when the issue…

Hi @Kay Multhaupt, That is very well possible. I hope you get support soon! In the meantime, I would recommend you to remove the screenshot from your previous post or make the site / account names unreadable. This is a public forum, so not the best place to share credentials! kr. 

Hi Josh, Maybe you could consider moving your JSM issues to a Jira Software project through bulk change. That way they remain in your system. Project permissions will let you limit access to them. You will lose certain JSM specific information in the process, then (SLA's, Request types to name a few). Or, as an…

🙌

Hi @Soporte Atl , If the user is an external user (and so: a customer), notifications are sent through the Customer Notifications section in project settings and not through the notification settings. Those only send out emails to internal users. If you want to send specific notifications to external users, you should set…

Hi @Kay Multhaupt , In order to request and activate your cloud trial licenses, follow the steps described in this support article. If you are still experiencing issues after you have done so, it is best for you to reach out to the Atlassian purchasing and licensing team directly. Hope this helps! 

Hi @Nagendra Shastry and welcome to the Community, Actually: you don't. Story points are a concept to indicate the relative size and/or complexity and/or value that you deliver in your project. As long as you haven't completed your story, you haven't really delivered anything. Your question indicates that you would…

Hi @Imad Alabed, JSM has a mechanism for tagging content in the knowledge base, but that links to the request types (or forms) in your service desk instead of users. To apply your example, in Confluence you would add labels to your articles: patients or clinicians. Then, in the project settings / knowledge base, you can…

Or for user stories: accepted theoretically means that Acceptance testing is complete, while done actually means that there is no work left to be done on the issue. If you don't need that distinction in your process, feel free to modify the workflow to your needs, as @Fazila Ashraf describes. You should adapt the workflows…

There's actually 2 options here: either the URL brings you to the issues page inside a project, where the default page you are directed to is the open issues list. The JQL for that is simply: Project = <your project> And Resolution = Unresolved Or the URL directs you to the advanced issues search as I explained in my…

Hi @Hayley Wang and welcome to the Community, The Jira URL and Jira Query Language (JQL) are totally different things, so I wonder what you are trying to achieve ... While a URL is the address of a web page, JQL is the language Jira uses to search for issues in the system. In other words, they serve completely different…

Hi @baoming yu and welcome to the Community, It seems you are trying to create a ticket in a certain project or of a certain type and the desired options are not available. That points towards either a permissions or configuration issue in your team's Jira instance. That needs to be resolved by your team's Jira…

Hi @Cường Trần , If you have a Confliuence space linked to your service desk as a knowledge base space, you should be able to do this directly from within your JSM ticket. On the right hand side of your ticket screen, under details, locate the option to create a kb article: Just follow the steps on screen to add an article…

Hi @Hannes, Just spin up an additional test cloud site and activate the products and plans that you use in your current cloud site. You get a trial license for 30 days. Backup and restore your current cloud site into that test site. And then migrate from your server environment into that test site. Hope this helps! 

Hi @Magda Michalak and welcome to the Community! Just map the done statuses of both your task and story workflow to the rightmost column of the board. If your project is team-managed, you can do so from Project Settings -> Board. In a company-managed project, this is from Board Settings -> Columns. Hope this helps!

Hi @Noam Guttman, Yes, they will just remain as sub-tasks of the story.