Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Question for ACP-100 Exam

Bektas Ozan Topkaya December 21, 2024

Hello all

 

I am preparing for the ACP-100 exam, and this question is confusing me. Shouldn't the third correct answer be 'workflow' instead of 'field context'?

Thanks
WF_TESTPREP.png

WF_TESTPREP.png

1 answer

0 votes
Lucas Modzelewski _Lumo_
Atlassian Partner
December 21, 2024

If you would think of it in terms of workflows - it’s clear that they can either be different or the same, most probably the same since issue types seems similar. (But migrating from 1 workflow to another is simple, statuses just need to be mapped)

However, when it comes to field context, if you have one field used across both issue types but with different options, that becomes a challenge. It would require some additional decisions and effort if we choose to proceed with this.

Bektas Ozan Topkaya December 21, 2024

It is not possible to use a field in the same project with different options.

But probably 2 similar issue types can have different workflows. When they are almost similar. conditions, behaviors, postfunction, proberties can reject.

Lucas Modzelewski _Lumo_
Atlassian Partner
December 22, 2024

damn, then I would get it right, but for the wrong reasons ;)

I've looked into it, and here is a part from the docs:

  • Set a globalcontextmake the field available in every project that exists on your instance. This option won’t be available if the field already has a global context configured.

  • Set a project-specific context—limit the field’s usage only to those projects where you actually need it.

We recommend limiting the availability of a custom field to the projects that will actually use it. Large numbers of custom fields with global contexts have a significant impact on system performance.

S: https://confluence.atlassian.com/adminjiraserver/configuring-custom-field-contexts-1047552717.html

and later on that same page:

If you delete a context, the field will be removed from any issues configured in this context.If the field doesn’t appear in any other contexts, you’ll permanently lose all field values. The deleted data can't be restored.

so basically it easy to lose data:

The real gotcha is that you can't move the issue to a different context without losing the existing values. 

S: https://community.atlassian.com/t5/Jira-questions/Re-Merge-multiple-custom-field-context-for-a-field/qaq-p/2222298/comment-id/561226#M561226 

Like Walter Buggenhout likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events