John Funk Community Champion

Great! Glad you go it working. And you are welcome!

It looks fine to me. :-)

Hi Rilwan - Just to clarify, they will not become Agents as that is a licensing thing. But you are right that they will have the Portal view simply because they have permissions to to see the issue. @Ander - Why do you not want them to also have the Portal view? They can see so much more information in the regular issue…

Hi Martina, No, you will not be able to modify the screen. I suggest you open a support ticket with Atlassian for their feedback. https://support.atlassian.com/contact/#/

Hi Ugor - Welcome to the Atlassian Community! I suggest you open a support ticket with Atlassian to see what they can do. Please post the resolution back here for future readers. https://support.atlassian.com/contact/#/

Nope. You will need the app. 

You are doing two checks/conditions back to back that contradict each other. Your rule with never make it past them. Those should probably be IF/ELSE conditions and then move the Create Issue actions under the appropriate condition. 

Hi Karine - Welcome to the Atlassian Community! Also, if you would like to work with an Atlassian Solutions Partner for that, feel free to connect with me through LinkedIn: https://www.linkedin.com/in/john-funk-92261a38/

Hi Yatish, Definitely, you should archive any projects that are no longer active. And yes, high numbers like that will impact performance. Also, if you have a lot of custom fields that use just a global context then that will also affect performance. 

Hi Mariana - Welcome to the Atlassian Community! I would be happy to discuss with you. My LinkedIn profile is: https://www.linkedin.com/in/john-funk-92261a38/

Hi Snehal, My recommendation would be to create a new issue and copy the values from the trigger issue for those couple of fields. 

Hi Joshua, No, you are not able to do that. There is no hierarchy per se within Jira Admins. Everyone has the same permissions. 

Hi Santhosh, You can add a looping transition on the Done status (a transition that starts and ends on the same status). Then add a condition that only the atlassion-addons group or project role can execute it. (Also add the Jira Admin group so you can see the transition later). Save and publish the workflow. Then you can…

Thanks, you, too. 

Hmm - can you share what you have? And how did it now work? What error did you get?

Hi Hassen - Welcome to the Atlassian Community! You should open a support ticket with Atlassian to see if your email address has been added to the suppression list. https://support.atlassian.com/contact/#/

You're welcome

You are very welcome!

Hi Francesco - Welcome to the Atlassian Community! You might be able to get what you want be creating Organizations for those departments and linking the users to the Organization. 

Hi Jeroen - Welcome to the Atlassian Community! No, you will not be able to change the criteria. Is there a reason you do not want to populate the Resolution field when completing an issue? 

Hi Yoon - Welcome to the Atlassian Community! You should open a support ticket with Atlassian to see if you are on their suppression list. https://support.atlassian.com/contact/#/

Hi Torben, I suggest your make your wishes known directly with Atlassian. https://support.atlassian.com/contact/#/

Sorry for the delay. I would use a different status for the Declined transition so you can keep those separate. 

Hi Ethan - Welcome to the Atlassian Community! Can you share the rule that you have so far and what is not working with it? 

@Soukaina IBALINE - Any luck?

Thanks for that. Then in your spreadsheet, put a column called Parent and put the key of the Epic for that story (e.g. ABC-123). Then also make sure you have a column for the issue key of the Story (ABC-678). Finally, you will have to do the import through the System Settings path: Settings > System > External system import

You need to add a Branch for Linked issue, and then put a condition under that to check that all of the issues are completed. 

Have you tried removing it from the Issue Layout? 

Hi Solomon - Welcome to the Atlassian Community! Since these are two distinct teams, I would leave them in two distinct Jira projects. But then I would create a new board that uses a board filter which shows issues from both projects. This is all assuming that both projects are Company-managed projects. 

Well, I am sorry to be the bearer of bad news - but the rule is not even running because you are over your limit for rule for the month. You can see that note in the bright yellow banner. Hopefully, that will start over for your on August 1, but not sure when your month begins and ends.