For this case, you can also check the Issue History for Jira app. My team created it as a journal for all past actions. It's not like a JQL query, but you can monitor changes for any standard or custom field. Filter issues by dates, projects, assignees, etc.
Issues created are marked with dots.
You can check if the add-on can help you with a 30-day free trial.
Is that showing created after a calculated period I.e. 2days after a custom date as per Gaurav’s question?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can choose any custom date or date range, and get change logs and issues created after that date. It is not the exact query, but might also help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK
very useful plugin,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The there no native function in JQL to add days to a date field
i.e. you cannot say Created > Planned Dev + 2d
You can calculate date diffs in automation. You could set a rule to set this as a custom field on issue creation or when Planned Dev is updated
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
is it possible that i can set a rule like this
If any story created on EPIC post Planned dev start that can automatically update the label "New discovery " on the newly created story
what could be the steps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As a guideline, you will need to verify some of the syntax an options inside automation as you go.
You can set up an automation rule triggered on issue creation. Depending on your setup you may want to limit the projects in scope.
You can check the issue type is Story
You can get the value from the stories Epic using a smart value
{{issue.epic.[Custom Field]}} - Returns the value in an epic's custom field. For example, if the epic has a custom field called Initiative, then {{issue.epic.Initiative}} will return the value in the Initiative field.
You can test the date values
{{issue.created.isAfter(issue.epic.[Custom Field])}}
There is an automation action to set issue values such as labels.
See
https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#--
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I recommend starting with a Manual trigger to run the automation on a ticket in order to resolve the syntax. Add lots of audit log actions to check values
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.