Guilhem Dupuy Expert

Hello @Jon Myers , There's nothing else I can think of; I know it's not the answer you expect but have you tried raising an issue to the Atlassian support Team ? https://support.atlassian.com/contact/#/ They usually are really helpful and answer quite quickly !

Hello @Keith Pritchard , As far as I know, there is no limitation regarding the number of issues you can import at a time from a CSV, Let me know if it helps, Guilhem

Hi @Bernd Lockermann , It could be; It depends on the permission scheme the project is using; you need the browse project permission to see it in the dropdown hence be in the correct group or projet role. You definitely could check that !

Hello @Bernd Lockermann , Is the project you want to share the configuration with of the same type than the others ? By that I mean, isn't it a Jira Work Management or Jira Service Management projet ?

Bonjour @Nadica Lakaliska , C'est possible grâce aux règles d'automatisations (natives sur Jira Cloud, accessibles via un Addon gratuit sous Jira Serveur ou Data Center). L'addon gratuit depuis Jira Serveur ou Data center est le suivant…

Unfortunately, to my knowledge, there is no way to do that natively on Jira, You can check for an app that may fulfill your requirement from the Atlassian marketplace : https://marketplace.atlassian.com/ 

You're Welcome, happy to help :) 

Oh, then I'm not sure of the result you can obtain using these Properties, I'm trying to figure out what in this default Workflow could trigger this message; You can try an other transition property : Key : jira.i18n.submit Value : resolveissue.resolve I'm not sure it's going to work but it's the last idea I have :/

Hi @Claire Nelson , I think you can add this blue message from your Workflow, by adding the following property in the desired transition : Property Key : jira.i18n.title Property Value : resolveissue.title Let me know if it works, Guilhem

Hi @Ben Weisman , Yes I confirm, when you discard a Workflow it only suppresses the changes you've made since the last saved version !

Hi @zigojacko , Yes it is; you can do that by creating a new queue, and adding as the JQL request "order by updatedDate DESC" in order to display on top the most recently updated issues Let me know if it helps, Guilhem

Oh I see you're using a next-gen project, Then indeed you can't set up resolutions in these projects, you can upvote the following demand to Atlassian regarding this mater : https://jira.atlassian.com/browse/JSDCLOUD-8523 Then I guess you could still go for the Automation option, or switch to a classic project which might…

Happy to help ! You're welcome Claus

Yes, it's the "Update issue field" post function, where you select the "resolution" field and set it a value. Then your resolution date should be set when you transition to the status. Here is an exemple of my transition to the "Done" status : 

Hi @Claus Østergaard Pedersen , You're welcome :) I know it's not perfect, but unfortunately, as far as I know there is no way to obtain the information you need in Jira. Maybe you could try with the "Workload Pie Chart" gadget if it's available in your instance (it may come with the Tempo app so I'm not 100% sure you'll…

Ok I see, then are these fields in the correct screen for the desired issue type ?

Hi @fredrik.froojd , Normally, you should be able to retrieve the "Resolution Date" field which corresponds to the date when the resolution was set in your issue. If no resolution is set, then you should add a post-function setting the resolution in your Workflow. You could also create an automation rule which copies the…

Hi @Brendan Gray , This feature is quite new in Jira Cloud; First of all you need to be a Jira Administrator to edit this setting; the go to your project settings >> issue layout menu. By editing the layouts associated with your issue types you'll be able to chose which fields are hidden when empty / always displayed. Let…

Hello @Claus Østergaard Pedersen , Indeed that's a though one, you can try using the "Burndown Chart" gadget from a dashboard; Then, you would have to go to your board settings, in the "Estimation" parameters and select the "Remaining estimate and ... " option : Then your burndown chart should decrease depending on the…

Hi Edmond, Maybe it is because you don't have the same issue types in your new project ? In Jira, you actually affect a Workflow Scheme to a projects, which links one or several Workflows to defined issue types. As a result, if you don't have the same issue types in both WF it Could explain the issue. Let me know if it…

Hello @Döndü Türkmen , You can achieve this using Automation for Jira, which is a free plugin on Jira Data Center. Using this add-on you can create an automation rule that will change your parent task status when all of its tasks are complete. Here is an example of automation that would achieve what you want to : Let me…

Always a hard choice to make between values and people appreciation ! It shouldn't matter so much but we are social beings and we are meant to try to connect with each others. If you're not choosing your values you might one day loose what makes you special !

Ask them. Transparency is the key to happiness and life-long relationships

Okay thank @David.Guemes it's clearer now ! To sum it all up, no there is no direct solution for that, there exist some complicated workarounds only like the one I explained. Otherwise, you can still "hide" these "None" values by creating a filter excluding the subtasks and by using it in your gadget. To create the filter,…

Oh, okay, yes it's a pretty advanced workaround and you need at least Project Admin permissions to execute it. I'm not sure to understand everything, it doesn't make sense to me to group an Epic by project; an Epic is an issue type and a Project contains issues. That's true that an Epic from project A can be linked to…

Hello @Deepthi , you need to be a Jira admin in order to do this

Ok I see, this one is kind of a pain in the king as you can't properly do this in Jira even though it is obvious that the subtask should be linked to the same Epic than the task it was generated from. I guess you could achieve that by using an automation rule; create a text field called "epic-link-copy" for instance that…

Okay @David.Guemes I understand better, But then, where do you want your subtasks to appear, as they are not linked to any epic ?

Hola @Sistemas e Innovación Digital ! Primero disculpa mi espanol, estoy aprendiendo :) Creo que el problema viene del esquema de notificaciones, ahi se cambian las reglas de notificaciones y de los relacionados correos . Necesite estar un administrator del proyecto para poder editarlas. Para exemple la notificación…

Hello @David.Guemes , If you select the Epic Link statistic type the subtasks will automatically appear in the "None" section because, as you said, they are not linked to any Epic. You can for instance select the "Issue type" statistic that will display every issue without any "None" section. Hope it helps, Guilhem