John Funk Community Champion

Bonjour Joris, Pouvez-vous également inclure une capture d'écran du journal d'audit lors de son exécution ? Êtes-vous sûr que cela ne s'arrête pas à la condition ?

Hi WB, You can't connect using the Epic Name, you will need to use the Key of the Epic for the Parent field value. 

Hi Rosalind - Welcome to the Atlassian Community! Just click the Send feedback link on the bottom left menu.

Hi Enmanuelor No, you cannot with the out of the box gadget. You would need to investigate an add-on from the Marketplace.

Not now, there isn't. :-(

Hi @Aswathi D - If you have the account ID, you can go to User Management, the select a user. Once on the user, replace the account ID in the URL with the account ID that you originally copied and then hit enter. It should show you the name. 

@rmax - Yes, it is a type of Custom Field. 

Hi @011_avinash Yes, this is expected behavior because the Systems Setting does not override the personal settings. 

Hi @vl2 - Welcome to the Atlassian Community! You should be using the Parent field now and not “Epic”. If you look at the history of the issue who does it say is clearing the field?

Great! I am glad that worked for you

Great! I am glad that worked for you

Hey Osama, the only way I know to do this would be within an app like ScriptRunner Behaviours.

Hi Jedsada, You just need to add multiple statuses to your workflow and then add Approvals to the appropriate statues. 

Hi Ravitheja, This is a bug in Jira where you can't edit the description for a custom field once you add one. You will need to update the description for the custom field in the Field Configuration used by the project. 

Olá Paulo, Suspeito que você também possa ter o Jira Service Mangement, que permite ter 3 agentes livres. Mas se você já tiver 3, não poderá adicionar mais usuários do Jira Software, mesmo que sejam menos de 10. Retire um dos usuários do Jira Service Management para que haja apenas dois lá. Então você poderá adicionar mais…

Hi Nuria, Are you using a Jira Work Management project? Because if you are, you can't see the proper breakout for Sub-tasks in a project Timeline. 

Great! Glad to help. 

Hi Christian, In the space for the edit of the Description field, put in: {{issue.description}} - "your text" where "your text" is the part you want to add to the original value. This will keep the original value of the field and then tack on your text from the rule. 

Hi Harvey, How are you opening Jira? Do you save a bookmark and you are clicking on the bookmark? If so, you probably have the issue tacked on to the end of the URL. Just edit the bookmark to clear everything out past .net. 

Hi Pierre, I would copy the rule that you have and make it just for Epics by adding a Condition as the first step after the trigger. Condition for issuetype = Epic. Be sure to check the box on the Rule Details page for "Check to all other rule actions to trigger this rule." Then you probably want to change the first rule…

Hi Christian - Welcome to the Atlassian Community! I would suggest you submit a support ticket to Atlassian: https://support.atlassian.com/contact/#/

One option would be to create a new custom field and not place it on any screens or forms. Then use automation to create a rule to move the data from the current field to the new field for historical purposes. Then delete the old field. 

Hi Manjula, You should be able do this with an Automation Rule. Just do an Issue Created trigger for the project then an action for Edit Issue. Select the Organization field and base it on the email domain of the Reporter. 

Hi Okan, I don't think there is an easy solution to this. You might see if an Atlassian Marketplace app could do it. You could create an advanced (ProForma) form that has conditional sections in it, but you would have to have a section for each Organization and the associated values. So if there are a lot of Organizations…

Hi @AS - Are you saying make them automatically active on the Date 1 and then automatically deactivate them on Date 2? 

Hi Mark, I see that you are on the Free plan, but I don't think that's the problem (though it might be). Try going to Settings > System > External System Import and do the import through that path instead of through the Filter/Search function. 

Hey Craig, I don't know that you are going to be able to do much about this. Just changing the Notification Scheme will probably not do it. While in Jira, you can click on your avatar (either your initials or an avatar) in the upper right side and then choose Personal Settings. There you will be able to click on or off the…

Thanks for the info, Phil. I think you should go ahead and write up the use case(s) for the error and submit a ticket to Atlassian to review and hopefully, fix. Glad you got it figured out and thanks again for providing what you actually had to do to make it work. 

Hi Chris, Not completely following the scenario without screenshots, but if it is no longer used, just delete the custom field. Or at least clear out all of the values for that project. 

Agreed, you should uncheck the box in this case. But your argument that the rule will not work because it "runs the risk of the user" going to none at all doesn't seem valid. If they are tied to an organization, then the rule will add that Organization. If they are not tied to one, then it will not, because well they…