John Funk Community Champion

If you are on the Sub-task issue itself, and then click on Move, you should see this: Is that not what you see? 

I would also suggest Jira Work Management as a lighter version to get started. Currently you can only do one form per project though and you can only have one Issue Type in the workflow for the board to work properly - but there are ways around that. 

Hi Trena, It could be a variety of things. Is the user receiving any emails from Atlassian at all? Check the Notification Scheme to be sure the user is incorporated to whom should receive emails for different events. Have the user check their Personal Settings to make sure everything is checked as needed:

Hi Barbara, Click on Projects and select Create Project Click on Jira Software on the bottom left Choose Kanban or Scrum Click on Use Template button Click on button for Select a Company-managed Project Put in a Name and Key for the new project Check the box for Share settings with an existing project Select the project…

I would like to see what it was really like in the first century AD in the Middle East and the Roman Empire. 

Glad you are up and running again!

Would love to see Ancient Egypt! Just visited the Giza Great Pyramids a little over a year ago. 

Going to show my age, but here goes:

But you have to decide what type of link the parent link will use. Usually something like Blocks or Depends On. What are you using between Master Epic and Epic?

Hi @이창호 - I would check to see if there are any post functions on the transitions in the Sub-task workflow that might be firing. 

Hi Sergio - what do you mean by Dummy is the level above User Story? Outside of an Epic not such parent level exists. So, have you just linked the issues using a particular link type? Can you share the rule that you have so far? 

I see this bug that says they will not be fixing that smart value if I am reading it right. https://jira.atlassian.com/browse/JRACLOUD-74208

Hi David, If the user is not getting emails at all from Jira, I would open a support ticket with Atlassian to see if their email address had been blacklisted for some reason. https://support.atlassian.com/contact/#/

So, you want to populate a new custom field with some static text for old issues (issues that existing before the default value (static text) was added? If that is the case, why don't you just do a Bulk change to update all of the issues? 

4. Those who enjoy eating pineapple all by itself just because of the glorious fruit that it is. 

Hi Seetham, I am confused by what you mean by "default value" . Are you wanting to copy the value of an existing field into the new custom field? 

Hello and Welcome, Maureen! We are glad you are here!! That sounds like it would definitely be a weird feeling. We have been back in the office for over 13 months so I would be going stir crazy by then. Again, welcome and enjoy the Community!

Seems like a donut kind of day

Hi Diane - If you select the option for Move, you will see the ability to change parent on the next screen. 

Hi Yen - Welcome to the Atlassian Community! Be sure that the new issue type you created is included in the Issue Type Scheme that the project is using. It will not show up if it is not in the Issue Type Scheme. Go to Settings > Issues > Issue Type Schemes

Hi Sujith, Often times the notice goes to a different email address that people are expecting it to. There is a Billing Contact for each instance which may or may not be the same as the Jira Administrator. Check with others in your organization to see if they have received the email. Also, you can submit a support ticket…

Hello and Welcome, @RACHAN KP ! We are glad you are here!!

Hi @Yan Cesar Rodrigues de Melo - You can do that with Issue Level Security. Just set the security for the current user = assignee or reporter or a custom field. Here is more information on issue level security: https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html

You will need to add a status for Discarded or whatever your like to call it. Then add a post function to the transition to this new status where you set the Resolution to Won't Do. 

For Team-managed, you can go to Project Settings > Access and add the user with the access you would like to grant them. But you will need to check the Permission Schemes used by the other projects to make sure they are using permissions attached to project roles that do not include the client user/group. 

Hi Arcolia - we use a status called Discarded with a Done type status category. The Resolution is then set to Obsolete in our case - or you could set the Resoluton to Won't Do or something similar. 

You add filters to boards, not projects. The filter will include the project. 

Hello and Welcome, York! We are glad you are here!!

Hi Yasser - Welcome to the Atlassian Community! Is this a Jira Service Manager project? Or a Company-managed project? 

Happy to help! And I hope that works for you. :-)