Jack Brickey Expert

check the status of Jira Labs under personal settings under avatar

Assuming you are on cloud as that is where the new jira issue view comes into play? are you on a Classic project type or Next-Gen. This view does not apply to Next-gen. If you are unsure a screenshot will help.

Cloud is same. You need an auto add on app.

Try creating a new from scratch workflow and associate. Something isn’t making sense here. Add an extra status so that when looking at the issue workflow it will be clear you are indeed using the new workflow. In the end you may have to create a new project, test to ensure it works, move a single issue, test it then move…

Note that natively JSD email issue management is a bit limited as you can’t map fields. If that is important you may wish to consider and addon like JEMH or other.

I don’t have any personal experience with any. Here is a search I did but nothing stood out at me. Cloud is rather limited for addons in this area.

Unsure of cause yet but here is what I would try next. * Hypothesis: something is squirrelly with the issues moved from NG. Test: create new issue in the project and try transition. * Hypothesis: something odd/unseen about the workflow. Test: create a dedicated transition without any restrictions from ToDo to InProgress.…

According to the details provided in the issue you included above you should toggle the Sprint feature.

First are you sure the WF shown is indeed the one associated? Can you verify by going to the detail issue view for one of the To Do issues and click on the View Workflow link by the status? Assuming it is the same workflow please recheck the inability to transition.

@Lee, is this a Trello or Jira Service Desk question? The reason I ask is that you have posted in JSD collection but reference Trello. You also have tagged: bitbucket, confluence and Jira.

@John Choate, welcome to the Community. Your question is rather broad. Is there a specific issue you are having or are you simply looking for best practices? i would suggest that as a PM you might want either a Dashboard or a Kanban board or both. There is some good documentation available on Atlassian’s site you might…

At this point I would suggest you reach out to Atlassian Support so they can examine and explain. I know that system accounts do not count as billable licenses for my (cloud) instance and when last I was on server that was the case as well. There may be a perfectly reasonable explanation for the error you are seeing that…

you are on cloud and using Next-gen project. For these project you cannot (yet) control when the issues in the Done column disappear. That is controlled by the SW w/ the default of 14d before removed. On a separate note congratulations for knocking out so many issues in such a short amount of time! ;-)

what url? The url is provided by Atlassian with every instance you create. If you need two completely independent urs then you would have to manage two instances of Jira and the two would not be linked in any manner. I doubt that is what you want or need.

So I was chatting w/ other champions and one of them pointed out that this is not associated with an addon at all but it is a System user. These definitely should not count against licensing. Please count up your non-system users. here is what i see in the User Management screen if I hover over the "System" label

so it appears to be the Embeddable Widget. I would reach out to their support and ask about this.

that seems unfortunate. what addon are these associated with? depending on that it might make more sense to me. 

You can share a specific project with the consultant group without sharing all projects. However, if you require a different URL that would be a different instance of Jira altogether.

If it is already optional then check the associated workflow to ensure There is no “validation” configured for OE during the transition.

You could use a dashboard and the two-dimensional gadget to illustrate reporter on y-axis and maybe status on x-axis. Or you could consider a pie chart. There are other gadgets so recommend you play with this and see if you can meet your goal.

You could consider exporting data project by project and importing. However this is just the issue data. You would need to recreate the project in the new instance. Given it is a trial instance I would expect the effort to be small.

Have you considered using Confluence and Knowledgebase? 

@Elizabeth Jones, based upon the bug Kurt mentioned I would guess they updated your instance and you are part of the “soaking” that is happening now. @Kurt Werner, given they are “soaking” the fix it should be soon. I also noted the workaround of toggling the feature off and back on so you might try that if you have not.

yes it is because u r on NG.

i'm guessing you are using a Next-gen project which does not support the Epic Name field yet. 

fix-versions/releases are not yet available in NG. At least it wasn't there the last time i checked. you can watch this roadmap page.

those six boxes are only an example of the new portal UI. As Victor mentioned you need to be an admin and if you are you can turn the new view on as follows: * go to the portal (main help center) and click Customize button * toggle on the new help center view what shows up will depend on what projects you have - one…

I just ran a test w/ another user and indeed they also see the start sprint and control lines and are able to manage the sprint just fine. So this says there is something specific to your instance. Either it is a browser issue OR it is a bug. either way I would suggest you reach out to Atlassian Support Please update this…

@vicm, sorry again for the confusion. I'm working too many things at once. Are you the owner of this project, i.e. did you create it? I'm believe you need to be the owner to manage the sprints. While there may be a way to give others the ability I don't know if that is possible. With that said, a couple of things I find…

Yikes! My bad! It is indeed. I guess I need more coffee. :-( let me do a couple tests on my side and get back to you in a bit.