Dick Community Champion

Hi @Vincent DESOUTTER Welcom to the Atlassian Community. Sadly, the custom fields in the Data Center lookupIssues function haven't received the love they deserved yet. It will not work. You can read a workaround in the answer to a community question that @Bill Sheboy kindly provided earlier. Kind regards, Dick

Hi @JT QA Welcome to the Atlassian Community Jira distinguishes 3 levels of administrator-ship. From the top down, there's: * Organizational Admin - in charge of product access (access to Atlassian products) * Jira Product Admin - in charge of a Jira instance and project access * Project Admin - in charge of project roles…

Hi ibm.kustagi@mercedes-benz.com We're here to help you in reaching the answer to your question. Although Google often is our friend, we're no librarians here. You can best start your journey at the Atlassian docs on how to extract field values from Jira work items. Kind regards, Dick

Hi @Sara Beyer We discussed this quite extensively on slack. Are there parts still unclear? Kind regards, Dick

Hi @florian_correll Welcome to the Atlassian Community There are ample possibilities here. Using Automation, you can send yourself an email with the content of any selection of Jira work items you can think of. The content of those items can be assessed and put in said email using smart values. Kind regards, Dick

Hi @Aggeliki K , Your example is similar to what @Walter Buggenhout described in this forums about a form with two interdependent dropdown lists. Be sure to work on a company managed project, as you need to have access to custom fields. Kind regards, Dick

Thank you for the update, @bhulka it's really appreciated. Kind regards, Dick

Under the hood, these programs have a lot in common, as they share a similar query language. A date can be stored in a {{variable}} , that can be manipulated in a similar fashion. Kind regards, Dick

Hi @Zulaiha Welcome to the Atlassian Community, First up: there's three levels of admins (each with a respective control span): * project admin * product admin (Jira) * organizational admin (all Atlassian products) Depending on the admin you talked to, your access might not be under their control (only the organizational…

Hi @Joseph Veal-Briscoe There's an Atlassian doc on how to sum-up x days to a date. Kind regards, Dick

And that same page also shows that it's not supporting custom fields. sigh... I knew that, but forgot it. Kind regards, Dick

The basic construct (from Atlassian on field editing ) { "update": { "description": [{ "set": "a new description" }], "labels": [{ "add": "test-label" }] }, "fields": { "summary": "woohoo! a new summary" }} The elements in the array should have curly braces (in bold) and a string "value": is put in too much: { "update": {…

Hi @Sachin Rohra The backlog isn't just a list of work items. It's a ranked list by the product owner, who carefully puts the most pressing matter at the top of the backlog, which signals the to the team: this has to be done first for either: 1) The next sprint (in case of Scrum) or 2) When taking on new work items…

Thanks for reporting that in @Ari Raatikainen , and providing the correct answer. I've reported the error and linked it to this community question. Kind regards, Dick

You should set the status of these tickets to "Done", with a resolution of "Won't Do". That way an audit trail would know that someone took the trouble of evaluating the necessity of the task at hand, regardless of the outcome of that person's decision. Kind regards, Dick

Hi @Karan S Welcome to the Atlassian Community, There's a comma too much within the square brackets belonging to the "content": [ ] bit. Your element within (nice boundaries with curly braces, is followed with a comma that would suggest another element. But there is no second element, so the parsing goes wrong. Kind…

Hi @bhulka Welcome to the Atlassian Community To the best of my knowledge, the bearer token and the user's email should be combined to a set of credentials first, as described by @Pramodh M in this answer. The captcha's only kick-in when there's too much false logins occurring (which would be triggered by your approach).…

If you encounter any difficulties, put them here so that we can solve them. Kind regards, Dick

Hi Paul, If someone would go and implement the stuff you have using the excel plug-in. What are the key things they need to do to get it working for them? I'm sure you'll be helping out someone with that stuff. Kind regards, Dick

Hi @Ari Raatikainen A small search goes a long way: Atlassian on Update Multiple Choice Fields Kind regards, Dick

Hi @Paul Beatrice Why don't you describe your current settings here, so anyone with a similar question could find an answer? It could also become your place to fallback to if something were to go awry in the future. Kind regards, Dick

Thank you @Bill Sheboy for the nice additions. Greatly appreciated, Dick 

Hi @Paul Beatrice Welcome to the Atlassian Community It seems like you're calling Jira from another program (Excel). Configuration of this setup is essential for it's functioning properly (think API-call using credentials). Without learning any of this and your specific set-up, answering your question is not possible. Kind…

Hi @El You can use boards as issue sources in the configuration of Advanced Roadmap Plans. (use the cogwheel to access the configuration of the plan). Otherwise, you can use a combination of the board filters : project = IB and component in (DEV, Ops) Kind regards, Dick

Hi @Mogtaba Moutasim Adam Alsheikh Welcome to the Atlassian Community Please remember The api-token is not universal: It can only pull the issues that the account, which made the token in the firrst place, is allowed to view. Kind regards, Dick

Hi @binay_yadav There's a string comparison operator called match, so you want to compare the content of your CVE field with the external CVE string similar to this: {{#if(issue.customfield_xyz.match(".*(CVE-abc).*")}} would match with CVE-abc you can replace the CVE-abc value with a smart value {{testCVE}} that has it's…

In addition to what @Mohamed Benziane mentions, it is good practice to have backed up your database before doing any deletions at all. But you knew that, I know. What you maybe didn't know is that there are ways now to have a local copy of your cloud database. Here's the Atlassian documentation on that. Kind regards, Dick

Hi @Niklas Malmberg The manual list order is achieved in JQL by using : order by Rank @Daniel Ebers wrote a nice article about how to incorporate sprints in a JQL query. Maybe that can alleviate your woes a bit. Kind regards, Dick

@nalams If you don't want the issues visible (at all), then why don't you move them to another project before moving the others to the desired new project without these bug/task issue types. Keep it simple for yourself. Kind regards, Dick

Hi @Caitlin Armer The reason an automation would not execute is a more general one: The automation has an actor, that should be allowed to be able to see the Jira item. Make sure this actor has a role in your project that allows it to execute the edits. Kind regards, Dick