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

How do I assign issue from new issue view?

I'm talking about https://confluence.atlassian.com/jiracorecloud/the-new-jira-issue-view-938040503.html

Assignee field is read only, I can't change it. This makes this new view completely not usable

Also, Story Points field is read-only too...

2 answers

1 accepted

3 votes
Answer accepted

This is your configuration, not the new view.

You need to talk to your administrators and make sure that the assignee and story point fields are on the issue type's edit screen, and that you have the permission "assign issue"

@Nic Brough _Adaptavist_

This is definitely not a configuration - I can assign tickets and change Story Points value using the old view.

Like # people like this

Same thing happened to us. The Edit screen did not have assignee before, but we could assign from the Old view. We could not assign from the new view until we added the Assignee field to the Edit screen.

You need to add this field on the edit screen of the dedicated issue type. 

This new view is bull***

We have solved this issue - that was a configuration after all (can't provide details - the configuration done by other people in our organization)

But to be honest - this is terrible UX when this new screen requires some additional configuration to work as old one.

UGH. I spent hours on this. 

Hey

Any suggestions on this? this is still an issue...

Taylor Atlassian Team Apr 22, 2018

Hi @Viktor Zozuliak, I can help you out with this. Do you mind answering a few questions so I can resolve this for you.

  1. Where are you viewing the new issue view (board / backlog / or full page)? Does this occur everywhere?
  2. Do you have a screenshot you could provide?

 

This is likely due to the configuration of your 'screen config' for that issue type in that project. The old issue view actually overrides some of these settings so that you do not notice it when you remove assignee / story points from the screen config (depending on the location - like the backlog for story points). In the new issue view, it is much more direct mapping to the 'view and edit operation - screen config'.

So if you are seeing the field but not able to edit it, I would check the 'edit operation - screen config' for that issue type and project. Could you confirm that both assignee and story points are on this configuration setting?

Thanks in advance!

Hi, @Taylor!

 

This happens everywhere - on every screen. This happens not only for me, but for a plenty of other guys in our organizations who also had this available in the old view.

 

Here are the screenshots:

Screen Shot 2018-04-23 at 13.01.42.png

Screen Shot 2018-04-23 at 13.02.01.png

 

As for configs - I don't have access there. Could you please provide a step by step instruction how to get there so I can share it with our jira manager? I've already reached him directly but he has no clue how to fix this...

Taylor Atlassian Team Apr 23, 2018

@Viktor Zozuliak Do you mind sharing the issue type ? Thanks for raising this for us, I'm sure I can get to the bottom of this and fix this soon.

As for the config steps, let's try this.

Step 1: Click on settings within the project (issue/board) you are in. Should be on the left-hand nav.

config_step1.png

Step 2: Within project settings, click on the screens option from left hand nav. Here you can see the specific issue type scheme's applied for each issue type within this project. 

config_step2.png

Step 3: Let me know if the view and edit operations are using different screen configs (the default would have all 3 operations (create,view,edit) the same but they can be configured to be different). 

config_step3.png

Step 4: If you can see the field but cannot edit it, that leads me to believe the assignee is not on the edit screen config. Try adding it and see if you can edit the assignee field now.

Final note: Can you confirm you can or cannot edit story points on the backlog but not the full page or board? 

@Taylor I don't have access to these settings, I'll communicate your message to appropriate person.

 

As for issue type - this happens for all issue types - Bug/Task/etc

Ok so I see the issue.

This new view doesn't allow editing of assignee if its not added to the configuration. If its not added it still appears in the new view but doesn't allow changing of the assignee. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

202 views 6 7
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