Vishal Biyani Expert

@Amanda TAY With Scheduled, you will have to specify the JQL. Since there is no issue trigger, you are getting the error in the way lookup is being used. Note that there is a limit to number of rows that can be handled via JQL. * What is the reason you are not going for field update trigger? * what is the business reason…

@Dinesh S R Check with your JIRA admin if you have required permissions

@nsherega JIRA doesn't allow exporting history. there are two options * Use REST APIs if you don't mind programming * Use marketplace apps

@Rutuja Patil if you go to view settings, there in Sort by you have various columns (including due date) for sorting. see if this works for you See this article if it helps you. Customizing your plans | Advanced Roadmaps for Jira Data Center 3.29 | Atlassian Documentation

Generally, subtasks are related to a story or task. The expectation is one story/task should complete in a sprint (unless there are reasons beyond anyone's control). You can go through this article related to this topic.

@Anjana V K Have you tried implementing hooks like pre-commit hooks in bitbucket to enforce a pattern in the branch name? if that pattern does not work, then branch creation can error out. See if this article helps https://confluence.atlassian.com/bitbucketserver/using-repository-hooks-776639836.html

@Kaladin Stormblessed Go through this article that talks about integrating git hub with JIRA. See if this helps. https://support.atlassian.com/jira-cloud-administration/docs/link-github-workflows-and-deployments-to-jira-issues/

@Joshua Vega Are you using some bookmarks that are no longer valid? Can you clear your browser cache and try again to see if issue is resolved?

Looks like you have few subtasks. You can filter it out using issuetype not in subTaskIssueTypes() project = MYPROJECT AND statusCategory != Done and sprint is Empty and issuetype != Epic and issuetype not in subTaskIssueTypes() See if this works.

if you try to exclude Epics from the above query, then does the count match? project = MYPROJECT AND statusCategory != Done and sprint is Empty and issuetype != Epic

@Aran Singer Welcome to the community! Can you share the screen shot of your automation rule (in a single image) so that community can suggest?

What is your build system? Is it Jenkins or something else?

Yes.

@Praveen Can you share a screen shot of one of the workflows where you are seeing status has changed from Open to "To Do"? Most likely renaming the status back to Open should help fix the issue.

Epic is an issuetype and JQL is written based on that. Similarly, you can write JQL for your Components. It could be one component or it could be multiple using in clause

@Fatima AlZarooni When you run the JQL, what do you get project = MYPROJECT AND statusCategory != Done and sprint is Empty

@Swetha Rao Pothapragada On the backlog, click on Quick Filters -> Manage Quick Filters There you can create a quick filter as per your need. Have you tried that?

@Daniel Dayan Try with 21600 (3600 * 60) The import file can look like this. Then import it using "import issues from csv". This will create a new issue of type Story. if you want to update an existing issue, then you can add existing key as Akash mentioned. I have tested with 21,600 in my instance and it correctly updates…

@Deb Keene in my opinion, it will be better to create a separate workflow for Task and Bug so that you can put a validator condition before the issue is transitioned for the specific issue types. Transitioning an issue back to previous state is complicated using automation rules

@Jonathan Bobo are you missing a # before lookupIssues? {{#lookupIssues.assignee.distinct}} Can you share the SS of your automation so that it is clear what you have created so far? Also, share the audit log showing the values in assignee variable. Just to ensure that this smart variable is not clashing with JIRA defined…

@Dilna You need to associate Story Points with the screen to resolve this issue. As Project Admin, * go Project Settings -> Screens * Issues -> Fields -> Actions -> Edit Fields * Search for field -> Click on Screen * Associate the field with the screen either Default or your project screen * This should resolve the error

Can you share the screen shot of the rule that you have written so far? if not try with this approach and then let me know where you are getting stuck You need to use Field Value Changed and select golivedate field. Then check if issue is Epic Then branch to child. and update the field in child issues.

@Eric Roetenberg As far as I remember, this change was brought in to align with SaFe hierarchy. As long as you are not deleting Epic from your instance, you should be fine. Any specific reason, why you are not using Epic at all. It can be placed above Feature and you may not need new issueType = Initiative

This is strange as I can see it in my Cloud instance when i try to import the issue from Admin. See below SS under Issue Fields

Looks like you have a marketplace app Rich Filters for Jira Dashboards that you want to use. Is that correct?

@Karen FitzGerald _ICT Programme Delivery_ Can you share more context as to what business problem you are trying to solve? How will the automation be triggered? if it is going to be scheduled, then it has a limit (i think 100) beyond which it can't fetch the issues Epic can have child issues (like Story/Task etc). Are you…

@Ashish Ranjan History searches are not allowed on label field. Therefore, as far as I know this can't be achieved using JQL

@Saad Ahmad Importing status is not feasible via bulk import as different projects may have different transitions. once the issues are imported, you can use bulk transition to move them to correct status. Alternatively, you will need JIRA Admin privileges to use Settings -> System -> External System Import > CSV. You will…

@Bozhidar Stoyanov In the example given (Unix or Mac), if you use curl, then, replace {propertyKey} with key say department, give the accountId for which property needs to be set give the user name and API Token and in data block give the key value pair. Once you run the curl command, the property with value will be set…

@Tiago S. Can you check the original time estimate entered at subtask level? Do you see 1m or 1h in subtasks?