Comments
-
Subtasks cannot be moved without moving the parent Story. It is best practice to scope your stories so that they can be completed within a sprint. If your stories are too big to be completed in a sprint, consider breaking those into smaller stories with smaller scope.
-
Hello @Jackie Lariviere Welcome to the community. I suggest you use the Automation feature for this.
-
For clarity, where have you configured "hours per day"?
-
I strongly suggest you open a support case directly with Atlassian about that. https://support.atlassian.com/contact/#/
-
(Looking at the chat between you and @Dave LIAO ) If you are using a given Status in multiple workflows, changing the Name of that status will change its name in all workflows that use it. If you want the Status Names to be different between projects/workflows, then you have to create new Status values and incorporate…
-
Are any other issues of type Bug displaying in the backlog? Have you identified any other issues that are missing? Can you provide a screen image of the missing issue? What is the status of the issue? Are other issues with that same status shown in the backlog?
-
Hello @Paul Kennedy I am assuming these are Company Manage projects. Is that correct? Go to each project and select Project Settings. Then select Workflows from the navigation pane on the left. Compare those screens between the projects. They are either sharing an entire Workflow Scheme, or with the Workflow Schemes they…
-
Unfortunately, no, as per https://jira.atlassian.com/browse/JSWCLOUD-17371 You could create a board from a saved filter that was based on a Team Managed project, but the board would not behave the same nor look the same as the board originally created with the Team Managed project.
-
Hello @Jassim Al Rahma Welcome to the community. If you would like to suggest an enhancement to the product you can do that through the Give Feedback option under the Help menu in the product. Or you can go to Atlassian's backlog for the product and search to see if the suggestion already exists, and (if you have…
-
Hello @soubirou Welcome to the community. Can you provide more information about your scenario and what you are trying to accomplish?
-
Are you working with Company Managed projects or Team Managed projects? The management of permissions for each is very different. For a given project, what are the permissions that your vendors need vs. what your employees need?
-
Are you working with a Company Managed project? If so, you need to remove the field from the Screen associated with the Create action for that issue type in that project. That can be done only by a JIRA Administrator The screen may be attached to the Create transition in the workflow, or it may be in a screen attached to…
-
Did your exported data include the Comments and Linked Issues and Attachment information? Did you map those to fields when going through the import steps?
-
Hello @Steve Gehlen I am not finding any documentation specific to migrating from Team Managed projects to Work Management projects. I think it would be similar to migrating to Company Managed projects, but I'm not really sure since we don't use Work Management projects.…
-
Hello @Daryl Chen Since that is a third party product, have you tried reaching out to that vendor's support organization?
-
I am not encountering that problem in my JIRA Cloud Standard instance.
-
As a follow up, this is the issue in Atlassian's backlog asking for the ability to use Automation to move issues in Team Managed projects from the Backlog to the Board. https://jira.atlassian.com/browse/JSWCLOUD-21481
-
I think the issue is actually in issueFunction in issuesInEpics() The subquery there is selecting the project that contains the Epics, but the issues in those Epics could be in any project. It seems like adding the additional clause of projects in ("20+ projects listed") AND ...should've addressed constraining the projects…
-
Here is the issue for that: https://jira.atlassian.com/browse/JRACLOUD-76529
-
Hello @Benjamin Hockenberry Welcome to the community. There are several posts in this community concerning the "A newly created issue must start in the To do status category" problem you are encountering. I'm trying to find them and see if they call out an issue in Atlassian's backlog about this problem.
-
Is this for a Company Managed project or a Team Managed project? For a Company Managed project you will have to make sure that the Story Points field is included on the Screens that are set up in the Screen Scheme for displaying Bug types of issues, and also in the Field Configuration for in the Field Configuration Scheme
-
Are you working with a rule for a Team Managed project or a Company Managed project? The field for denoting the Epic "parent" of a Task may be different than the field denoting the Task "parent" of a Subtask. In Company Managed projects "Epic Link" is used to record the "parent" Epic for a Task rather than the "Parent"…
-
What is the issue type of the issue you are searching for? The default issue hierarchy in Team Managed projects is Epic > Task > Subtask In Team Managed projects you can add additional issue types, but they are added at the same level as "Task". Only issues from the "Task" level will be displayed in the list in the…
-
To apply this to specific issue types you will have to create additional workflows so that you have a workflow where this validation is used and a workflow where it is not used. Workflows are grouped into Workflow Schemes and within those schemes you can assign different workflows to different issue types as well as having…
-
You might want to look at the work @Andrey Legayev has done with a custom script, mentioned in this post and in the comments of the Atlassian issue about the New Issue View. https://community.atlassian.com/t5/Jira-Software-questions/How-do-I-make-the-old-view-permanent/qaq-p/1678292#U1686080…
-
Does the issue you are looking for have a value in its Resolution field?
-
Could you possibly have more than one field called "Story Points"? You should be able to tell by starting to type "Story Points" in the advanced search JQL field. It will list all potentially matching fields. Is this for a Company Managed project or a Team Managed project?
-
Hell @Rob Smith You could use a CSV import to import the issue information, each time you need to replicate it. Alternately, there are a few apps in the Marketplace that focus on cloning issues. You'll need to research them to determine which one meets your needs. I have not used any of them myself so cannot speak to the…
-
Hello @Dominik Maslanka Welcome to the community. I am unclear about what you are trying to do when you say "separate tasks from sub-tasks". Can you provide more description for what you are trying to achieve? Describe what the end result would be.
-
I can't speak to your JSON issue, but have you tried exporting to CSV an issues that is already in JIRA that contains a tabular format, and then using that as a template for creating the CSV import data?