John Funk Community Champion

Hola Pablo, Puedes hacer esto con un formulario ProForma cuando el usuario envía el ticket, pero no puedes hacerlo dentro de la pantalla de Jira. La aplicación ScriptRunner Behaviors podría hacer eso.

Hi Darshil, Are you linking the issues when you clone them? If not, you need to. Once they are linked (or if they are already linked). Create an automation rule based on a Field Value Changed trigger based on the Feedback Due Date field. Then add a Branch for Linked issues. You can specify the issue link type if you want.…

I think that looks fine. Especially if it solves the problem and gives you what you want. 

Hi Morgan - Welcome to the Atlassian Community! The way we handled that was to create a set of predetermined equipment by either Position or you could create a custom field with drop down values like Package A, Package B, Package C, etc. Then the Reporter would select a Package or populate the Position field (also a drop…

See my answer on the other question you posted. 

Hi Vincent, I have always had good success with Issue Security schemes. Doesn't really depend on the developers/project members - they either see the Issue or not. That's all the work of the Jira Admin. If a user has the ability to set the security level, then that's just a field the set - very easy. 

Hi Lorenzo, Don't get confused that projects not showing in the Location field for the board means that the projects cannot be "linked". By linked I assume you mean that you want issues from those projects to appear on the board. That is based on the filter the board uses, not the Location field. So, if you create a board…

Hi Laura, My understanding: For now yes. If you purchase before the split it will always be included. After the split, you will pay separately for each. 

Hi Anagha, Where does this already existing workflow exist? If outside of the same team-managed project then no it is not possible. 

This is not completely correct. Please see the answer by @Marc -Devoteam- 

Hi Kate - Welcome to the Atlassian Community! It is probably because those tickets use an issue type attached to a different workflow. While on the board, click the More link on the upper right and then Workflows. There you will which Issue Types are using which workflows. While the List screen shows all issues, the board…

Hi Akshay, You need to add the Task issue type to the Issue Type Scheme used by the project. Settings > Issues > Issue Type Schemes

Hi Sneha, There's not really a way to know that which I am aware of. The hope is that whoever created the Service Account would have done so we an adequate name to tell the difference. And the Human Account should be someone's name. Of course, the base behind all of the accounts is just an email address. So you might be…

Yes! That looks good. Give it a try.

It's probably best to go ahead and open a support ticket with Atlassian. They can better get to the bottom of this since they have access to your environment. Please post back here with the resolution. https://support.atlassian.com/contact/#/ Good luck!

For Data Center, yes, but not sure on Server. Could you not find it? 

I don't believe it is possible to include it in the email body. But you might ask Atlassian Support about that. 

Go Settings > System > Outgoing Mail (under the Mail heading). Make sure that is enabled. 

No, you can do all of the fields at one time. 

It shouldn't be. Does it do that on all of the Show more links? Have you tried more than one? 

Okay, that doesn't make sense. So you went to that same page and clicked on Show More and that's what you got? Maybe click the Refresh icon there in the audit log list (top right) and then click on the show more. 

Hi Jeffrey, No, the Issue Type Hierarchy is applied across the entire site. There is only one Hierarchy so whatever it is must be applied to all projects. And, so if you change the existing one, it will affect all projects using it. 

No, I mean click on the Show more for the success and capture that. :-)

Can you post a screenshot of the details of the Audit Log where it runs with success? Also, do those email addresses get other emails from Atlassian/Jira? Oh, and since it is a dev instance, make sure that email sending is turned on globally!

Hi @Nagavenkateswararao Soma - Welcome to the Atlassian Community! Yes, that is a system field and should not be modified. Plus it is an extremely complicated process that Jira uses to populate the Rank field behind the scenes. There is a Global Rank type custom field if you are interested in that. However, the real…

Hi Harbans - Welcome to the Atlassian Community! You will need to create a couple of date type custom fields - waiting for when the flag gets set, and one for when the flag is removed. Then you can create an automation rule based on the flag being removed, and you can do a diff between the two dates to get the amount of…

Hi Eszter, If you are wanting to copy fields down from Epic to children and then from the children down to the sub-tasks, you will need two rules. This is because the branches will fire at the same time and not in sequential order. So I would do the first part of the rule that you have and delete the second Branch. Also…

Hi Alexander, You will probably have to use the Summary field in the Request Type form, and then don't add any other fields. Then do the rest of the fields in the ProForma Form. 

Hi Tejas, Take a look at this article and see if it helps you. https://community.atlassian.com/t5/Jira-Service-Management-articles/Reading-a-Forms-ProForma-field-value-without-the-JSON-tab/ba-p/2097012

Hi Kavitha, You might also consider the Revyz Configuration Manager for Jira app to help with that. Or the more robust Revyz Backup and Restore app to also move data. You can find both in the Atlassian Marketplace. Full transparency, I am an advisor for the apps.