Jack Brickey Expert

While I do not yet use, I have researched Insight and likely will incorporate into my instance at some point.

This topic has come up before in the Community. Here is one thread that might be worth reviewing. I would definite suggest researching the Marketplace for the right addons.

Your question is a bit confusing. if you want to export all issues created since the beginning of the year use this JQL... createddate >= startofyear() then use the esport function to push to CSV

If the user has ever had any issues assigned, reported, etc by them then the avatar will still show. I don’t think there is a solution for this.

I would create a CSV file of all emails and paste it into the add customers dialog. Generally you can get this from IT or HR.

in Jira projects and versions are 1:1. I believe that the Portfolio product supports 1:N version:project but don't have direct experience.

i would be surprised if that worked but never have tried so would be interested in results. :-)

Hi Rodrigo, welcome to the Community. This has been asked and answered previously. If you look to the right under Recommendations the first one is a good example. That conveyed, no you cannot do this. There was an old suggestion for this capability (JRACLOUD-31618) that was declined.

missing the screenshot. Are you saying you want to change the name of a Request Type? You mention Issue type but they don't apply to portal or rather are not viewable in the portal where as Request Types are. You say the box is greyed out. Which box? In portal or in the application.

so I'm guessing you are using Portfolio? I do not and am not familiar with how initiatives works TBH. If this is the case I would add portfolio to your tags.

this seems quite strange. I would check to ensure you are indeed not a watcher or somehow associated w/ the issue (reporter, etc). If you are sure that you are indeed not tied to this issue then I would contact Atlassian Support to have them log in and have a look.

Correct. I too am not happy that this capability is not available in the new issue view. I and others have provided feedback on that and I believe there is an open suggestion at Jira.atlassian.com for this. You might search there and vote/watch the issue.

Be careful with making fields required. Rarely do you want to do this. Rather you should consider adding a Validator to the specific project workflow as part of a specific transition, e.g. Create. If you make a field required and it is used by multiple projects then you must expose that field on every screen so that the…

Hi Marc, I’m a bit confused by your question. Can you please elaborate? Where and how are you viewing issues? Are you on a Kanban board, advanced search, etc.

And that is how it is designed to work. Unless something has changed SLAs are not displayed in the portal. If you have an example of that not being the case I would be interested in seeing it so my understanding can be updated.

I can’t say if Atlassian will implement in the new issue view or not. I suspect there is an active issue reported at Jira.atlassian.com but haven’t looked. Note that you can, as a work around, use the advanced issue search to export an issue.

I suspect he has been deactivated. Have you check the deactivated users under User Management. If a user show in the drop down then he would have to exist in the list. Note deleting, rather than simply deactivating is not an good idea. If you do plan to delete then use JQL to find every instance of the user (reporter,…

VYou might consider reaching out to a local Atlassian Partner.

@[deleted] , I’m unclear on what field is not displaying. You say the “field status” in one instance and then you refer to “workflow”. I s the field in question a default Jira system field or a custom field? Note if indeed you mean Status and it isn’t showing that would be weird. If you mean the old Workflow link that…

Hi Amanda, you can do both simply by creating a filter using JQL. Something like below. project = abc and creator = customerXXX Now, for display purpose if you wish to monitor the number of issues then consider using the above saved filter on a dashboard leveraging one of the many gadgets, e.g. pie chart, created vs…

If you use swimlanes by queries then that is what you will get. You must create a query for each individual query. Everything that does not match any of the queries will fall under “everything else” swimlane. If you want swimlanes to exhibit epics then use swimlanes by epics. if you want epics to disappear from the board…

there is a link icon you can click on. 

unfortunately this isn't possible in the new view AFAIK. I would suggest putting in feedback via the link.

resolution shows just to the right of the status once DONE.

I would probably use two different Issuetypes (Internal, External) and have different screen schemes for the two so you could have the appropriate field required. Another consideration - use a cascading field: * Internal* A * B * C * External* 1 * 2 * 3 and make the field required via the create transition validator. 

edit the queue, copy the jql text, go to advanced search for issues, paste in the jql, update columns as desired, export to csv

i expect you are using a next-gen project if that is the case.

I guess my question remains whether you are seeing SLAs on the portal or not. The first image is from the portal and is what I would expect to see. The second is from the JSD application and is what I would expect. The third would tell me that if an issue is created that doesn't match any of your goals then there will be…

You can estimate in the detailed issue view.

You need to expose Epic Link field on the edit screen for story. Added the epic into the Epic Link field. Or if you are using scrum classic then on the backlog expand the epic sidebar and drag story onto epic.