Shawn Masters Expert

Each Row? Like a numbered detail list? If so your best bet is to export the list and use the numbering from the excel CSV file. Otherwise you would need to build a custom field to allow you to assign a value to it and then Order By that custom field. 

I would do another export of those tickets to verify the issue ranking didnt modify on import. I would also pay attention to the values of the ranks, if you have gaps it may cause some odd behaviors. 

This can be handled in a large variety of ways....sticking to the issue navigator here is an Atlassian Article outlining "searching for issues" which should help you fine tune that navigator to provide you the results you are looking for: https://confluence.atlassian.com/jiracorecloud/searching-for-issues-765593657.html

https://confluence.atlassian.com/jirakb/epic-name-field-is-required-on-create-issue-screen-for-other-issue-types-779158642.html

Have you done an export of your current Epics to ensure your formatting of the CSV is all correct? This is a step i take when i run into import errors to ensure I havent overlooked a fields expected values in the Jira DB. 

Google Translate used: Esto no es todavía una característica. Ver enlace a continuación: https://jira.atlassian.com/browse/CONFSERVER-36786

This question falls more into a discussion category as it has multiple ways to solve it depending on your companies requirements. 2 things to get you off on the right foot: https://www.atlassian.com/blog/jira-software/jira-release-management-steps https://marketplace.atlassian.com/apps/1215460/automation-for-jira

Jira Worklow Extension add on can accomplish this multiple ways https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions

https://community.atlassian.com/t5/Jira-questions/Why-is-completed-done-work-carrying-over-into-a-new-sprint/qaq-p/761975

See related issues that were resolved: https://community.atlassian.com/t5/Jira-Core-questions/Cannot-set-value-for-locked-custom-field-Epic-Name-in-issue-BR01/qaq-p/69621 https://community.atlassian.com/t5/Jira-questions/Import-EPICs-Cannot-set-value-for-locked-custom-field-Epic-Name/qaq-p/950490

Based on their backlog it looks like this function has not yet been added. https://jira.atlassian.com/browse/JPOSERVER-202

In the cloud version of their software we have been falsely promised budgeting software and improvements. They have repeatedly said over the last few year "feature X will be ready soon!" and here we are Years down the road without even an update. The support is all over seas and takes several weeks to get back to you. The…

I would advise something like accello ...Tempo is one of the WORST vendors for Atlassian products Ive encountered. 

Not possible as an Anon user of Jira. Restricted to Jira Users/Admins of the instance

You can to an extent but not for budgeting purposes. Portfolio is more about capacity/road map planning ...atleast from what I've seen in our instance; if you happen to come across this sort of use case definitely let me know! 

Check notification scheme for changes Navigate to the ticket that the user is reporting failed to generate notifications Top of the ticket (next to the workflow buttons) IF you are logged in as an Admin there is a drop down called Admin Select Notification Helper Pick the user from the drop down Pick the event they…

Validate your user permissions - normally when i encounter this issue its due to the permission scheme not allowing the user access to the project to create issues or comments. 

We use Abacus for Jira Cloud in our instance - being on server you have more options but by default Jira doesnt do calculations. 

Answered here previously: https://community.atlassian.com/t5/Jira-questions/Generate-JIRA-Service-Desk-ticket-from-Exchange-Office365-quot/qaq-p/406576

This requires the Tech to go out and find the issues. While this is the end goal it does not provide a viable method of finding other issues that relate to the ticket being created. 

If you create the CSV file correctly you can import the fields into already made tickets OR create new tickets 

JWME Addon allows us to do this using Post Functions in the workflow https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions?hosting=cloud&tab=overview Additionally, Automations for Jira could accomplish this for you as well:…

What pieces of information let you know you need to review the issues? Your best bet is to have a dashboard or just a filtered query that allows you to pull the outlined issues above into your output. For example, are all of the tickets in a Specific "status" or do they are get Assigned to you? 

Are you using IE to do this by chance? Thats the only time I ever catch this complaint on my own Customer portal. 

Ah...its not quite intuitive but according to the documentation as Issue populate the board you use the quick filter and Group by to display issues you are looking for https://confluence.atlassian.com/jirasoftwarecloud/get-started-with-next-gen-projects-945104903.html Choose the best view for your board * Assignee…

Unfortunately, History searches do not support the 'Sprint' field. You might however be able to call down the change log with the Rest API to grab that info. https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-get-complete-changelog-for-a-issue/qaq-p/501636

Since the next gen project is isolated from the classic schemes you would first have to export and then import them. I havent had any other luck doing it yet 

Based on the First sentence in this document it looks like the Customer would need the "Service Desk Agent" Role/Permission https://confluence.atlassian.com/servicedeskcloud/adding-customers-852724126.html

Project Settings > Issue Types > Click on the issue type Drag and drop fields to customize layout 

As of right now you can only adjust their position up and down in the list of fields. https://confluence.atlassian.com/jiracorecloud/configure-field-layout-in-the-issue-view-961798123.html