Guilhem Dupuy Expert

Bonsoir, Malheureusement à ma connaissance, pas de possibilité de restaurer un tableau supprimé :/ 

worked for me too, thanks !

Okay Phil I understand your problem, indeed I confirm this is not doable in Jira, you have to choose one of the other solutions like using several different transitions for example

Hi @Phil Bustin , You can "hide" transitions based on Workflow Conditions. In your case, you should add the following condition in your "Any" transition : "User Is In project role" And select the "atlassian-addons-project-access" role which will allow only automation and other addons to see this transition (hence the…

Ahah lots of complexities in JQL so lots of ways to struggle sometimes Happy to help anyway! 

Hi @Chris Buzon , I think it didn't work because of the "=" operator, which checks for an exact date and time (as the resolutionDate is a date and time field). I checked this on my Cloud instance and the following JQL should work : resolutiondate <= endOfWeek(-10d) AND resolutiondate > endOfWeek(-11d) You can then adapt…

Hi @Ray Miller , You can definitely use this query in an Automation rule; You could schedule it (using "scheduled" trigger) to run once a day and, for all issues matching the JQL query, transition them to "Withdrawn" status. If you want this transition to be unavailable to users, you could add a Workflow condition on it,…

Hi @Tuncay Senturk _Snapbytes_ , Unfortunately this is not possible in Jira, However, you could parameter the values of your field like this. : "1 | value 1" "2 | value 2" So that in your excel export, you can easily remove the characters after "|" and get numbers as you would like. This is more an Excel trick than a Jira…

Hi @Pooja Patel , When you commit the change, accepting of of your scenarii, the changes you made on the issues in the scenario (start/end dates, Sprint, etc ...) will be applied to all issues in the scope. Hence if you edited issues from several projects the impact will be cross projects. However, I'm not sure about which…

Hi @PRAMOD KUMAR REDDY KASIREDDY , Unfortunately you can't trigger a pop up to appear when changing the "assignee" field. What you can do is add an auto-transition in the Workflow, called "re-assign", which will display a screen where the users will be able to change the "assignee" and the "sub delivery" fields. The…

Hello @Angie Affolter , To my knowledge there is no way to filter issues in such a way in Jira, But as a Workaround, you could add the field "subtask" to the column view of your filter, which will display something like this : As a result you'll be able to see for each task the linked subtasks. Let me know if it helps,…

Hello @Ray Miller , You can achieve this from the advanced search, filtering the issues based on the following JQL query : status = Withdrawn AND timespent > 0 Then, from the search menu you can perform a bulk change to transition issues to the desired status. However, a transition from "Withdrawn" to "Resolved" status…

Hello @Robert Varadi , You can parameter this in the Worflow, by adding the following property to the statuses where users shouldn't be able to add comments anymore : jira.permission.comment.denied This will disable the permission to comment issue for the statuses it is added to. Let me know if it helps, Guilhem

Hi @[deleted] , Darlene is right, If the documentation is not enough and you need help to configure your issue type scheme, you can ask your Jira Admin or contact an Atlassian Partner

That did the trick for me, thanks @Pramodh M !

Morning @Dorothy Callahan , This is because your issue is currently not in any Sprint, there is 1 existing Sprint in your project hence the "+1". If you include your issue into a Sprint, you'll see the name of the Sprint in this field :) Let me know if it helps, Guilhem

Nope it is not you'll get all functionalities without restrictions. You can try downloading it using this link, even if you're on Server I think the Data Center version should world. Please tell me if it does :) 

Okay, good to know it ended up working for you ! Best of luck, Guilhem

Unfortunately I'm no JSON expert, Are you sure getting the users in role 1 doesn't work ? I tried it on a test instance and it worked. Can you please try to add a comment in an issue with the following smart value and tell me what you ou get ?…

Hi @Chasovskikh Kirill , There indeed is a cumulative flow diagram that you'll find in the reports inside your Jira Software projects : Is it what you were looking for ? Guilhem

Hi @eric_legroux_consulteer_com , The Jira issue links work both ways; if you add a link on issue A saying it's "blocking" issue B, it will automatically mark issue B as being "blocked" by issue A. I think that's why your rule doesn't work, maybe try your script with only the inward link part ? Let me know if it helps,…

Hi @Alejandra Martin , To my knowledge there is no way yet to enlarge this list; that's why it's easier to start typing the name or the key of the issue you are looking for to reduce this list.

Hi @Kölker, Finn , Indeed you can not retrieve the EmailAddress from an insight User attribute from a smart value, this is weird as this works for every other User custom field :) The workaround you could use is the following : you can populate a multi-user custom field based on the users in the attribute "Role" of your…

Content d'avoir aidé :) Bonne journée Youri

Bonjour @Youri Soposki , Normalement les liens vers d'autres objets Insight devraient être visibles depuis la vue graph. Peut être que les autres objets Insight sont rattachés à un Utilisateur Jira et non à l'objet Insight "Utilisateur" ? Ca peut se vérifier de 2 manières : * Depuis un objet Inishgt "Utilisateur", s'il n'y…

Hi @jherman , Your request looks good, I think it's because you closed the "}" too soon; in your code, you close the update { before doing your field request. Maybe try after deleting one "{" before the part where you update the resolution ? Let me know how it goes, Guilhem

Hi @june_l , Maybe this comes from your permission scheme; do these users have the permissions regarding timetracking ? (the 5 permissions at the end of the permission scheme) Let me know if it helps, Guilhem

Bonjour @Absa Thiam , Pour cela tu peux créer un nouveau filtre du type project = "Nom du projet" AND issuetype = Bug puis le partager. Ensuite, depuis un tableau de bord, tu peux ajouter un gadget "Pie chart" basé sur le rapporteur qui t'indiquera le nombre de bugs assigné à chaque utilisateur. Pour le nombre total, un…

You're wlecome. If it helped don't hesitate to Accept the answer, in order to help the other members of the community to find the relevant information more quickly :)

Hola @Ester Cerveró Unfortunamente no se puede cambiar este parametro despues de la creation del proyecto. Lo que puedes hacer es crear un nuevo proyecto "gestionado par la empresa", parametrarlo como lo necessitas y luego mover tus incidencias hacia el nuevo proyecto Dime si te ayude :) Guilhem