Comments
-
Are you Tickets in just one project or more than one? What are the issue types of the tickets where you want this option to be available (i.e. Story, Bug)? In each project that contains the tickets you want to affect: 1. Go to Project Settings > Workflows 2. in the new screen, find the issue type(s) where you want this new…
-
Are you working with a Team Managed project or a Company Managed project? Can you show us a screen image of the roadmap and of an Epic that is not present in it but you think should be?
-
Try this project= example and status CHANGED TO "testing" BEFORE -2d AFTER -4d I figured this out referencing this document on Advanced Searching Operators. https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/#Advancedsearchingoperatorsreference-CHANGEDCHANGED
-
Are you clear now on how to add a new Status to the system, and to the workflow for your specific project? Or do you need additional help with that?
-
Hello @Michele Daigle What is the filter for your board? Can you show us the Columns page under Board Settings? This issues may not be appearing because - they are being excluded by the filter used by the board - the status that the issues are in is in the Unmapped section in your Columns page.
-
Hi Corey, Where did you find that setting? Are you working with Team Managed or Company Managed projects.
-
Hello @corey Be advised that Jira does not require you to name each sprint uniquely. You could have multiple sprints named "Sprint 1". If a user is updating the Sprint field directly on an issue, Jira also does not limit the sprints listed in that issue. So issue ABC-123 on Board ABC can end up assigned to Sprint 1 created…
-
Hello @Bill Kunneke There is not native functionality available for JQL for that. Are you open to adding a 3rd party app to your instance? Can you describe the problem you are trying to solve by querying for this information?
-
Hello @Joshua Buchanan The simple answer is that when you create an issue it will automatically go to the Status from the workflow designated by the Create transition. That is the transition between the gray dot and a status. Looking at you diagram you would need to change the target of the Create transition from the To Do…
-
Hello @Tanya Maslach There are two concepts here: 1. Statuses 2. Status Categories Statuses are the values to which you set an issue. These are customizable. Status Categories are ways of grouping similar Statuses together. These are not customizable. JIRA has built-in functionality based on the Status Categories that is…
-
You might want to look at this post for a solution that involves using a custom field.
-
Hello @Vinicius Zhu Welcome to the community. Currently it is not possible to have different workflows per issue type in the Team Managed project. You can comment on and vote for that change here: https://jira.atlassian.com/browse/JSWCLOUD-17434
-
Hello @Lena Post Welcome to the community. When you say the "whole" Jira project do you mean you want to clone all the issue in it also? Are you working with a Company Managed project or a Team Managed project? There is no single process native to Jira Cloud that would allow you to clone a project including both its…
-
Hello @chinmay konkar Welcome to the community. You can use the Automation feature of Jira Cloud to create a rule that is triggered by the transition update of the task. You can add to the rule a Branch to affect the Related Issues = Parent Epic, and then you can add an Action to the rule to make the change you want in the…
-
I have found additional limitation with this in how issues are displayed in the Backlog. I have not figured out if there are any work arounds for these issues. In Team Managed projects issues don't use the Epic Link field, but rather store the parent Epic issue ID in the Parent field of an issue. In Company Managed…
-
Hello @Florian Minterbauer You have it correct. Teams may choose to first estimate by Story Points to get a general idea of relative size of tasks without trying to figure out the actual hours needed to complete each task. This is typically done during Backlog Grooming. The team may then choose to estimate the actual hours…
-
How sophisticated do you expect the EmpID matching to be? Would you try to implement something that would consider "abc123" and "abc 123" to be a match? You might want to consider adding some validation to that field so that you are more likely to get conclusive matches.
-
What type of data is entered in the field? Are spaces or non-alphanumeric characters ever included? What version of Jira are you using and what version of Automation? I work with Jira Cloud. I might be able to work out a solution in Automation there, but that doesn't guarantee that the same functionality would be supported…
-
Hello @Sadath Ali Syed What is "EmpID"? Is that a custom field? If so, what type of field is it? I think it might be possible to do this with Automation, but to work out the details I need to know what EmpID is.
-
I recommend that you open a support case directly with Atlassian concerning this behavior. It may be a bug and they may or may not already have it in their backlog.
-
@Javanshir Mustafayev _ HIT Concerning your last question: Is there a tool to count the percentage of completed and due issues per user and per project? I can't find the percentage in the built-in functionality of Jira. You might want to look at the Issue Statistics gadget for the Jira dashboard to see if you can find a…
-
Hello @Michael Benedict Did you find an app to solve your issue, or otherwise come up with a solution?
-
Then an administrator of the project needs to go to the Releases page for that project and create a version, and then select that version as part of your issue creation. Or your JIRA Administrator needs to change the project so that the Affects Version/s field is not required, at least when an issue is being created.
-
Go to the Releases page for the project and see if there are any entries there in any states (Unreleased, Released, Archived). The message is complaining that there are no version defined. Does the UI allow you to save the issue when the field is set to None?
-
Hello @chad zibbel Welcome to the community. Please tell us what you have tried so far.
-
Hello @송원재 Welcome to the community. There is not a configuration to solve this problem. In Classic projects, the parent Epic information is stored in an issue's Epic Link field. The parent issue information for a Sub-task in stored in the Sub-task's Parent field. In NextGen projects, the Epic Link field is not used.…
-
Hello @Sadeesh Narendran I can't provide you with a complete answer, but I can provide you with more information to help you work towards a solution. Log Work is an event, not a field. When you Log Work you get a dialog that shows multiple fields including the amount of time to be logged, a comment field, a date on which…
-
Yes, this is possible to do for JIRA Administrators. If you want to change the data in an existing issue, you need to include in the import data the issue's ID - i.e. ABC-123. Then in the field mapping step, map that field/column to Issue Fields > Issue Key. If you want to add a new sub-task to an existing story, then you…
-
This post is a duplicate of https://community.atlassian.com/t5/Jira-Software-questions/quot-Affects-Version-s-quot-field-is-required-error/qaq-p/1722660#U1722876
-
Hello @Sridhar Mohan Welcome to the community. If you try to create the same type of issue in the same project through the UI are you required to enter a value for the Affects Version/s field? Generally the fields that are required for a given issue type in a given project are determined in the Field Configuration/Scheme…