John Funk Community Champion

こんにちは @菅澤 朱梨 - Atlassian コミュニティへようこそ! Jira Work Management 製品は、Jira Software 製品と統合され、製品としては Jira という名前になりました。ただし、ビジネス プロジェクト (古い Jir Work Management 製品) とソフトウェア プロジェクト (古い Jira Software 製品) は引き続き作成できます。したがって、今すぐビジネス プロジェクトを作成したいようです。 [プロジェクトの作成] をクリックした後、左上の [作業管理] メニュー オプションを選択します。これにより、ビジネス…

It all depends on how you classify bugs/defects. This is the way we handled it. When testing, if something is found to be wrong, we either created a Bug or a Defect. A Defect was a Sub-task issue type and was attached as a child to the Story. The meaning of Defect for us was that the Story could not be finished/deployed…

Is it possible to share a screenshot of the project roles for the project for that user? Which roles does the user occupy? And are they in the roles by name? Or as a part of a group?

What did Support say?

Hi Santhosh - Welcome to the Atlassian Community! I think you were under the wrong assumption as that’s not the standard Agile practice you describe. Tasks are Stories are at the same level, Tasks are not children of Stories. Same with Bugs.

If you are using Jira Service Management and invited them as customers which don't require a license, then that would work. But that is not Jira Software. 

Hi Bruno - Welcome to the Atlassian Community! I wouldn't advise that because they you have no single person responsible for the issue. If you proceed though, you would create a new user by inviting the distribution list as a user. That would need to have some way in your mail system to receive and email and validate it…

You don't put approvers in the workflow - you add approvals. In the Approval setup, you identify the field that will be used. Usually the Approvers field. But you add the Approvers manually or through automation. So, let's start with the first step - you created a workflow, but when you click on the status, there is no way…

Hi Rahul - Welcome to the Atlassian Community! License are sold per user not per team. So the answer is one license - one user.

Hi Henal - Welcome to the Atlassian Community! Can you share some screenshots of your rule and the error message you are getting? 

Is the workflow active? Because you can't add approvals to inactive workflows.

Okay, this doesn't look like anything in the article haha. There's multiple errors so it is a little hard to following. What are you really trying to do? And why was the article not helpful for you? 

Hi @justwow - Welcome to the Atlassian Community! I would just say to follow standard Agile practices and definitions. An Epic is a large piece of work that is made up of multiple stories, where the stories represent individual, deployable code for the most part. Components can be used to group or categorize you work -…

Hi @Stephanie Glynn - Welcome to the Atlassian Community! It's best to create a new question for your specific issue. What type of project are you using? Team-managed? Company-managed? 

Is this custom field type coming from an add-on? That is not a standard field type in Jira Cloud that I see. 

You can create a manual automation rule to clone into another project if you wanting to click. :-)

Very good - I missed that. 

Hi Jose - Welcome to the Atlassian Community! Go to Settings (cog icon in the top right) > Issues > Link Types

Hi Javi - Welcome to the Atlassian Community! You should open a support ticket with Atlassian and have them check the suppression list for the email address. https://support.atlassian.com/contact/#/

Happy to help - sorry I was too slow in responding to the substring question. Glad you got it working. 

Okay, instead of doing an Assign issue action (delete that) and just add the Assignee field to the Clone issue action and see if you can select a name there. 

Hi Clemens - Welcome to the Atlassian Community! By default, issues in sprints are not considered complete unless they are in the far right (last) column of the board. So you should map your Canceled status in that column also. 

Hi Owen, Xray is a third party vendor app, so the template does not include that by default. But it will certainly work with it once it is loaded. 

Hi Jannis - Welcome to the Atlassian Community! One option would be to place a transition screen on that transition that let's them know that they must have hours > 0. Otherwise, you would need a 3rd party app like JMWE or ScriptRunner to set up the validation with a message. 

Hi Julliane - Welcome to the Atlassian Community! You don't need to use cascading fields in the advanced forms, you handle that with sections. So you can have a dropdown with various values, and based on the value selected, you can show certain fields associated with that value. And make any of them mandatory at that point…

You are welcome!

No, the person must have an Agent license for Jira Service Management because those are the only persons who can change values of JSM issues or transition them. Customers do not have a license.

Please show the details of the edit issue action.

You are welcome!

Great! Would you be so kind to click the Answer accepted button to close this for future readers? Thanks!