Veera_zqt9p1 Atlassian Team

@Anto , You are right, when you mark an Epic as done, it'll not change Status or Resolution values. In Jira, there is another field called Epic Status which is specific to Epics and it's different from the Workflow status. "Mark as Done" action sets the Epic Status to Done. You will notice this in the history panel of the…

You are welcome @Taha Hasan 

You are welcome @dharm6619 

@David Loya It could be a different issue. Please submit a ticket in our Support portal with example Epic and the board in which you are trying to mark it as done so that one of our Support Engineers can check and get back to you.

@Sabrina Liao It's not the 'Edit Issue' screen. Screen linked to a particular workflow transition is different. Let me explain with an example. * In my JSD project, one of the issue types is mapped to workflow which has 'Resolve this issue' transition. * You can find the correct workflow which is being used from Project…

@dharm6619 there is no option to filter only body while making the RESP call.

You are welcome @Gerda Tilk 

You are welcome @[deleted] 

Users by default get "All" Fields option until they change it to "Custom". I wonder how the config changed to "Custom" for all those hundreds of users in the first place. AFAIK, there is no single place where you can change from "All" to "Custom" or vice versa for all users in Jira.

@[deleted] No, you haven't anything wrong. It's a known bug in Confluence which is being tracked here: CONFCLOUD-38181 Unfortunately, there is no known workaround as well.

@Terence_Rhoda It makes the field as required to be filled n by the user as well. Did you check if the users are using "All"/"Custom" as their default setting on the "create" screen > Field Configuration? If they are using "Custom", you may ask them to switch it to "All" so that you don't have to make the field as required.

In a nutshell you want to reset the SLAs once the ticket is moved to new project. Correct @Gerda Tilk ? It's not possible at the moment to reset the SLAs at the moment. We have been tracking this as a new feature in our Jira Service Desk Cloud version: JSDCLOUD-194 However, JSD server has a plug-in called Time to SLA which…

Hi @Marc Gotthardt , Try User Profile macro 

@dharm6619 I don't think you can get comment body alone directly from the REST end point. The output you shared is in JSON format. You can parse the JSON object and just extract body element value using JSON path: $.body in your script 

@Priyanka , "Start date" and "End date" seem to be custom fields to me. It's possible that the default value for these fields is set as "10/Jan/2020" It's worth checking the field configuration for those two fields.

@Taha Hasan , As far as I know, there is REST END point which can be used to create API token on behalf of a user. The tokens can only be created by individual users from their Atlassian account profile.

@Amit , Even though you are the org and site admin, by default you don't get access to all the projects. Being the admin, you can update the project permissions and get your self required access to the tickets.

@ramani_chandran When SAML single sign-on is configured with Azure AD, users won't be subject to Atlassian password policy and 2FA if those are configured for your organization. This means that any password policy and 2FA is essentially "skipped" during the login process. If you want to have 2FA enforced, we recommend that…

Good to know. Thanks for sharing @m_yumen 

@Terence Rhoda The behaviour observed here is as per the current design of the create issue dialog. In detail, * Initially all users get "All" Fields to show as their default setting on the "create" screen > Field Configuration. This will display all fields as per the screen configuration. * * Users might opt to switch to…

You are most welcome @sheldon lu If you are fine with my answer, please accept the answer.

Hi @Sabrina Liao I am able to replicate this behaviour at my end. This usually happens when the transition has a screen with resolution field added to it so that the user performing the transition can set the resolution manually, and also a post-function to set the resolution. With this setup 'Resolve issue' event is not…

@Juvenal Trajano da Filho From your screenshot, looks like none of the issues (standard tasks) have any sub-tasks created under them. Click on the 'Issues without subtasks 66 issues' show that it show those 66 issues on your board.

I completely I agree with you @Khairul_Neezam_Ramlee the bug should have been fixed by now. I like the workaround you mentioned. 

Hi @Sabrina Liao , Edit issue action in the automation rules comes with only a few options and Organisation is not one of them. We have been tracking this as a feature request: JSDCLOUD-4258 to include more options.

@Khairul_Neezam_Ramlee Here is most recent bug: JRACLOUD-73554 specific to date/time custom field.

@David Loya , I come across similar issue few times. This is due to a property setup in the workflow being used by Epic. In my case, I had jira.issue.editable property set to 'false' for one of the statuses (Done) in the EPIC Workflow. This means that when the Epic is in 'Done' status, the epic can't be edited. You can…

@sheldon lu , Workflow Validators can compare two date values. You can choose 'Date Compare Validator' option to compare two dates during a workflow transition and click on 'Add' button. In the next screen you will be able to choose two date fields and apply the condition. Make sure you publish the workflow changes.

@Khairul_Neezam_Ramlee Just realised you are using date time custom field. It's a know bug in Jira which is being tracked in this link: JRACLOUD-72350

@Khairul_Neezam_Ramlee , All the date & time values are stored in the UTC format in backend database for Jira Cloud. However, you can update timezone settings in Jira / personal level to view the values in your own timezone. System level default user timezone settings:…