John Funk Community Champion

I am John Funk and work as our Agile Tools Administrator at Ramsey Solutions. Always love to see what @Dave LIAO is up to. :-)

It's certainly easy to get lost in a sea of custom fields. Contexts are a must! And it gets really confusing if you add custom fields with the same name in multiple Team-managed projects. 

Hi Robin, You are missing a ( in what you have posted above. 

Hi @[deleted] - Welcome to the Atlassian Community! You need to add the Epic Name to the create screen you are using for Epics on that project. Go to Project Settings > Screens Click on the screen scheme and then the screen. There you should be able to add the field. 

Thanks for the Summary!

Excellent summary - thanks!

Hi @Guru Darbar - You should be able to accomplish this with an add-on like Automation For Jira or ScriptRunner.

Take a look at this guidance and see if it helps you. https://confluence.atlassian.com/advancedroadmapscloud/configure-your-instance-998650924.html

Hi @Olawale Ajibola - Welcome to the Atlassian Community! You can do this with Advanced Roadmaps, but you need a Jira Premium Subscription to get access to Advanced Roadmaps. 

Components are not currently available for Team-managed projects. You can vote for the feature request and follow it here: https://jira.atlassian.com/browse/JSWCLOUD-17601

Those are additional requirements that were not mentioned in your original question. You can simply add the Developer project role to the permission scheme for who can set the security level. Also, I am not sure that the security level would interfere with the creation of the issue using the API as it is added as a part of…

Did you change the project when you did the move? Or just the Issue Type? 

Hi @sri.rangineni , What type of project is it? You have to be a Project Administrator to be able to add a new Component to the list in a Company-managed (Classic Software) project. 

Well, in my opinion, that's exactly what it is intended to do - control access to an issue. I believe that is your intent unless I am missing something. And not sure what the API or resolution has to do with your question at all if you want to clarify that part. If not, not biggie. And, no, who can set or remove the…

Hey Sherrill - Welcome to the Atlassian Community! You can do a Move on the issue to change the Issue Type. Click on the 3 dots menu in the upper right of the issue and select Move. 

Hi @Wubing Ye - Welcome to the Atlassian Community! Go to Settings > Issues > Field Configuration 

@Hemant Jadav - YOU have to submit the support ticket as I don't use Data Center. It would do no good for me to submit it. 

Hi Tom - I have not seen this. Can you share some screenshots? 

No, you create a generic Security Scheme that is used across all projects and set the Security Level as a default so that it is automatically applied to every created card. 

Thanks for doing that - voted!

Why wouldn't that scale? 

Hi Yakub - Welcome to the Atlassian Community! Can you describe a little more what is not working for you after making the changes? 

This is actually a really good idea with life in general. REALLY doing a check in with your spouse or loved ones on a frequent basis as well as remember to check on offsite coworkers, friends, etc. 

Gosh, if we have to decide to use DACI or not, now it's 35,001 decisions for toady! :-)

Hi @Kshitij Yelkar - No, this is not possible and it is not coming back. Another option is to paste this to the end of the URL for the issue to get to the old view: ?oldIssueView=true

To be honest, I am not real sure. It might take using an add-on for the report. 

Hi Giulia, What type of project do you have? Team-managed project? Company-managed project? Or Jira Work Management/Jira Core/Business project? There is no Process Management type of project. So as the warning so, you need to make sure that the Due Date is on the Edit screen. Also, you need to have Assign Issues permission…

What a good reminder to review rituals. It is easy for them to become stale and common place.

@Travis Rebok - Any update?

Hi Isaac, One option might be to grant Browse Projects permission to all users for all 3 projects. Then add an Issue Security Level to each project uses a Project role. Then you can apply the same Security Scheme to all issues, but it will control access by being in a particular role in that project.