Comments
-
Go to the board settings and check your board filter. Likely has old statuses.
-
I would create a quick filter “has attachments”.
-
When you create the request types you can also create groups and add the request types into one or more groups. When the customer hits the portal they see the groups and if they click one they then see the associated request types where they can then create new issues.
-
@michal.gottlieb, first let me be clear that I do not work for Atlassian. I’m a user like you. With that said, in the roadmap you can and should add children to each epic. To do this simply click on the epic bar and on the right you will see a little ‘tree chart’ icon. Click it and add the stories/tasks associated with the…
-
Add “epic link” column Final Resolution brought back to the top so others don't have to read thru all the troubleshooting... This is a Next-Gen project and the Epic Link isn't displayed for those projects. Likely a bug that will be fixed at some point.
-
It depends on what you want to order by. In your image you see the “order by priority”. You can click the drop down and change the order by field. Now if you wish to “rank” the issues to represent the order in which you want them to be worked then you should use a board and enable ranking. Then drag the tasks into the…
-
They are separate functions. The roadmap provides a high level view of the epics that represent the chunks of work. The board will show the detailed tasks within all the epics. Unlike classic projects you cannot display the board in swimlanes by epic which would sort of achieve what you are asking.
-
You can’t do a drop down but consider using groups with request types. Sign In Issues: * a * b * c Access: * d * e * f
-
I really haven't spent much time w/ Roadmap TBH but wanted to provide this feedback. When I first looked at Roadmap I thought "Gantt chart". As such, I expected to be able to show/hide the children under the epic. This obviously isn't the case so i'm unsure how to really leverage the roadmap as yet. Another oddity is that…
-
Is there a good definition of 'New Jira 2.0' and what is includes. Most questions here deal with Next-gen projects but some deal w/ the new look&feel UI that is presented currently if Jira-labs is enabled. I think there is a need for clear terminology and definitions to help control the confusion people are feeling.
-
A number of people in the Community is asking about Next-gen and Roadmaps for Server. Any discussion about that possibility?
-
Yep so it isn't possible and the reason is due to the relationship Request Type has to Issue Type. That is the available Request Types are dependent upon the Issue Type. It would be good if you could do this on the Create screen but... NOTE: "Customer Request Type" = "Request Type" don't ask me why.
-
hmmm....just tried and doesn't appear to work. will need to check further. might not be possible.
-
go to project > project settings > screens and click the screen for Create. at the bottom click the drop down to add a field to the screen and select "Customer Request Type".
-
@Lukas Gonzalez, sorry i have been on extended leave. I would refer you to this thread rather than regurgitate it. The question is - are you allowed to comment on a closed issue?
-
Customers cannot see dashboards only users w/ application access: agents, admins
-
@Max, what is the latest on this?
-
If you are wanting to add a static icon to the UI then you would need to edit the code. There is not customization for this other than changing the favicon and logo on left.
-
a couple of things... * those aren't the ellipses i was referring to BUT... * you appear to be on server and as @Kimberly Deal _Columbus ACE_ indicates you should be able to click on the dates in cloud there are ellipses to the far right of the sprint
-
it feels like a bug. did you check to see if it works from the edit screen? If it works there and not in the board view then I would certainly reach out to Atlassian Support. I verified that this is not happening in my Cloud instance.
-
one last question - does the Organization clear if the agent transitions via the app or just when Customer invokes transition? Not sure what that will mean but data is data. :-)
-
I'm scratching my head on this one. I have certainly never seen the Organization field being cleared but TBH I do very little w/ that field and haven't monitored it before. I will reach out to other champions to see if they have any ideas and have them chime in here. You might also consider reaching out to Atlassian…
-
This is not possible since you can't create a board in Next-gen (previously known as Agility). The only board available is the default one that is per-project. I attempted to create a Kanban board and include a Next-gen project but it was not an option. you can provide feedback to Atlassian via the feedback link.
-
love my pets. I have two Carin terriers and and orange tabby. Recently my house has been a zoo w/ my son staying here resulting in 5 dogs and two cats. YIKES!
-
yes. go to the backlog view and for the sprint click on the ellipses and edit sprint.
-
you might want to add a couple of screenshots of exactly what you are seeing.
-
@Luka Zlatecan, as you have described it, this is very bizarre. There must be more to this. Can you open one of the issues into the view issue screen, edit it and try updating the Original Estimate field and see if it sticks?
-
@Andrew Lewis, your JQLs are flawed because there are no parentheses around the issuetype section. Replace w/ the following. * issuetype in (Incident, "Service Request", "Service Request with Approvals") AND priority = low * issuetype in (Incident, "Service Request", "Service Request with Approvals") AND priority =…
-
@Laurent MASCLIN, most of us in the Community are users just like yourself and can’t speak to any roadmap plans. The exception is if you see a lozenge by the poster’s name that says “Atlassian Team”. That said, you generally want see any communication about roadmap commitments here in the Community as it is the wrong forum…
-
No it doesn’t need to be active nor would you want it to be active IMO as that equates to churn. When you completed the sprint was the next sprint defined/created in the backlog? If not, before completing a sprint, create the next sprint then all incomplete should appear in the top-most sprint in the backlog rather than in…