Fazila Ashraf Community Champion

Hi @Venkat Jira Admin Yes , the site will be working for 15 days before it gets deactivated

Hii @yosi hatem You have to use the advanced edit https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ { "fields": { "sprint": 25748 } }

Hi @Inna S Unfortunately out of box, Jira does n't track historical values of custom fields and also not with relation to another field. The workaround you posted would be the best bet.

Hi David You can also share it directly to atlassian as a product suggestion -> https://community.atlassian.com/t5/Announcement-articles/We-re-changing-how-we-manage-feature-suggestions/ba-p/2328033

Hi @Yousuf Al Rawahi For cascading select you have to use the additional fields - json input format. See the KB https://confluence.atlassian.com/jirakb/set-value-for-cascading-field-with-jira-automation-1456179215.html for detailed instructions. Hope this helps! 

Hi @Andrey Ivanov That was interesting.. I managed to get that automation work

Hi @Imad Zerrouki Welcome to community! Are you looking to migrate data between organisations? i.e., by domain, you mean organisation? If so, refer to https://support.atlassian.com/organization-administration/docs/copy-jira-data/ 

Thank you @Mark Segall , @[deleted] ! This post solved this puzzle i was looking at. Long live the community! :) 

Then i would recommend you to immediately reach out to Atlassian support via https://support.atlassian.com/contact and explain the situation and seek support. 

Hi @Assist10 Follow the instructions to update payment or contact your site admin / the person who set this instance to do the same. "Atlassian retains data for deactivated products for 15 days for trial sites or 60 days for Free, Standard, or Premium subscriptions after the end of your current subscription period.…

Thank you for the update!

Hi @Prabhashankar Rai Welcome to community! In the automation, you can have if else conditions to validate different criteria which also are applied on your SLAs and then determine what should be the duedate and then trigger the creation?

Hi @Vibhor Kumar Agarwal Can you confirm that the user has 'Create attachments' permission to this project?

cool :) 

What is the issue type name in your site? May it is has an extra space or capitalisation difference?

For your requirements, it will be story instead of the Task in this example :) 

Hi @Boluwatife Adewole You are on the right path. Type the issue type name in the value field. Below is an example

This is not tied to this particular field but all empty fields to which a user do not have access to edit will not appear in the view screen for them. Yeah, i am not ok with such behaviour either but this is how it works :( 

Hi @Alina_Seitan-Todosiciuc Can you check whether those users who do not see that field have 'edit issue' permission? The fields that are not populated only show up for the users who have the Edit permissions. If a user doesn't have the Edit Issues permission, they can't populate the empty fields, and will only see what's…

Completed 😃

Hi @Kaladin Stormblessed Yes, Sprints are considered unique entities and are not related to projects but to issues. Actually there a frequent question that unintentionally sprints are shared by users…

Hi @Pranay Singh Welcome to community! Can you explain more? Do you want to achieve this requirement or this is something that is happening and blocking you?

Hi @Mohammad Hamadi Welcome to community! Referring to https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog-- , try using the below {{changelog.status}} - Changelog information for the Status field. This example shows the previous status for issues that are transitioned.…

Hi @Thuyen PHAM Not straight forward with out external plugins like Deep clone etc. With out plugins, you could try exporting the issue to CSV and importing it to the other site via csv?

Wow Thank you @Bill Sheboy .. didnt know that this was possible.. @mohit jangid , check this.. i would accept this.

@mohit jangid , I think you misunderstood the branching statement as 'For each assignee'. It would actually interpret as 'For each issues, assignee variable = smart value'. I do not see a way how you can achieve a single email for each assignee on all their due issues through automation. 

Filter -> assignee = currentUser() and duedate > now() If you use the filter subscription approach as suggested in my answer, users subscribed will get a daily email (or as per your schedule set) with the list of issues which are overdue and assigned to them. If there are no issues matching the filter that day for that…

Yes, For summary, the overview is for 7 days. Unfortunately this doesn't seem to be configurable/adjusted at this time. You may find the details in https://support.atlassian.com/jira-work-management/docs/get-a-summary-of-your-project/ . 

Hi @A.M.E.C Welcome to community! By 'Delivery date' is that a fixed date for the whole project or is it captured as a custom field for the give tasks along with the due date?

Hi @[deleted] The summary usually shows the statistics for last 7 days. For example, the issues which were moved to 'done' in last 7 days shows up in the 'Issues done' section. Do you find the issues in the 'list' view?