Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Logging Dev Board Story and Task to Epic When Creating Ticket

You can assign a bug ticket to an "Epic Link"  when creating the ticket in the Dev board. However, is there a way to allow users to do this for story and task tickets, without having to drag tickets to an epic after logging them?

1 answer

Hello @Vladislav Nivorozhkin 

Welcome to the community.

Are you working with a Company Managed (classic) project or a Team Managed (next gen) project?

It should be possible to do this in either. You just have to make sure the Epic Link field is available on the Create Screen for each type of issue.

Hello, this is a company managed project.

In that case, there is an Issue Type Screen Scheme assigned to the project which includes the screens that are used for different actions (i.e. Create and Edit) for each issue type in the project. There might be one screen used for all actions for all issue types, or different screens. The JIRA Administrator will need to ensure the Create screen for the Story and Task issues includes the Epic Link field.

The JIRA Administrator should also look at the Field Configuration Scheme for the project. Like the above scheme, the Field Configuration Scheme is used to specify what fields will be available to the different issue types. The field must be included in the Field Configuration(s) that apply to those issue types also.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

58 views 0 0
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you