Comments
-
issuetype options are associated w/ the project so if you only want Epic and Story then you need to change in project settings > issue types. Of course you can limit your Kanban to only show Epic and Story issues but that doesn't address the drop down.
-
not in NG projects at least not currently. you may wish to provide feedback via the feedback link
-
and if you do have sprints enabled then when you complete the sprint they disappear.
-
Not yet but stay tuned. Here is a thread on this topic.
-
can you share a screenshot of what you are seeing and illustrate what you 'were' seeing.
-
got it. thanks.
-
@Michael Sukharev, please consider selecting the appropriate "accept answer" as it helps other in the future. I suspect Nic's is the best answer for your issue.
-
@Ruben, welcome to the Community. I'm unsure I am following you completely here. What do you mean by "enabled the epics panel"? As well, you state "I cannot select this epic..." do you mean the epic name is not in the list or something else? Could you provide some screenshots of what you are looking at and are you using a…
-
@rgsilva-aegro, is this a Next-gen project or Classic? The reason I ask is I saw your same question on Jason's AMA for New Jira. While I don't use NG projects today except to play around with it, my understanding is that there are no user accessible board filters. I will assume you have a classic project for my answer…
-
Got it! i can’t think of a way to do this thru configuration such that the JSD SLAs rules would cease. I would offer two ideas: * add a reminder in your calendar program to update your SLAs * add a Jira issue with a due date and use automation to remind you
-
You would export from zendesk to CSV and then import. It is tedious but doable. It took me a couple days to migrate from Spiceworks.
-
Not sure I understand. What defines when an SLA expires?
-
@Michael Sukharev, if you want ready for release tone green (Done) then edit the workflow and select the status and change category to done. Now for burndown point, only the right most column will be counted as done for burndown so if you want to count ready for release as done for burndown then map that status to the…
-
no problem. I suggest you click the feedback link in your instance and let Atlassian know you are interested in this. If your question is now resolved be sure to click the "Accept answer" on this thread as it helps others when they have a similar question.
-
UGGGGGGGHHHHHHH!!!!! This is a Next-gen project isn't it. if so that is the issue. I think this is a know bug.
-
ok...well lets focus on just one because something isn't making sense. As it shows for me as you can see below. So click on say PE-68 and see if the detailed view is displaying the epic link of Unplanned/Support.
-
hmm, and you are sure that some/all of these tasks are associated to epics? can you show me a screenshot that confirms this?
-
correct Max! and this is one of the key 'selling points' of next-gen I think - giving all users the ability to create simplified projects that won't break other projects. editorial
-
adding to Max's input. Next-gen isn't an off on. It is a template used when creating a project. You can create a classic project and bulk move all issues from NG to the classic one. Secondly, there is a toggle for 'the new jira view'. It is called Jira-labs. You can enable disable under your avatar (bottom left) and…
-
@Cathy, try going to your workflow and click on the transitions that feed Escalate and Resolved (or similar) statuses and uncheck the box that says "show transition in the customer portal".
-
if the exact users email is indeed a Customer in the project (project settings > people) associated w/ the email handler then the issue should be created. Can the customer open an issue via the Portal? I would recommend reaching out to Atlassian Support
-
We have a winner. :-) The bug was fixed in 3.13.1 so I think the listed bug is your issue and you will need to upgrade to resolve. cheers!
-
yep. NG simply will not be able to replace classic anytime soon if ever. If your question is now resolved be sure to click the "Accept answer" above as it helps others when they have a similar question.
-
did you verify that the email for the incoming issue is actually a listed Customer? If you don't allow "anyone to send" request then the from email must be an existing customer.
-
this should be relatively straightforward. Here is something I use in my instance...
-
with cloud you are offered an email from Atlassian and was going to suggest trying it but w/ server this isn't available. i found a similar thread point to a bug - JSDSERVER-5778. can you check to see if it is possibly related? What version are you running?
-
You are most welcome. If your question is now resolved be sure to click the "Accept answer" above as it helps others when they have a similar question.
-
can you answer cloud or server? in Cloud you set up the channel in project > project settings > email requests. Server is a bit different and I'm guessing you are on server. have you actually logged into the email account to look at the inbox? Just a thought.
-
don't think it is possible yet. suggest you click the feedback and suggest it as it would be useful I suspect.
-
@Dan Vink, cloud or server? can you send a screenshot of what you are seeing and what screen you are running into this on?