Jack Brickey Expert

You can use the Automation feature to do this. Here is an example of what it would look like.

You may want to start with this article plan-your-jira-server-to-cloud-migration

let's hope not. i have pinged some folks in the forum so maybe they can chime in. Was this previously working and then you just went in to renew and now users cannot log in?

not sure i'm following. what do you mean by "cloud handler"? You could setup default values for required fields possibly.

I wish I could assist further but w/o access and seeing firsthand I'm out of ideas. The only thing I can thing is that the instance you are trying to log into is not the same as the one that has been renewed but just guessing here. I will ping other community leaders to see if they have any thoughts.

not sure why you are seeing the error TBH. Is the SW behaving normally otherwise? If so I would use the feedback link and share the issue w/ Atlassian.

that is what i meant by children. Once you link a story to an Epic it is in effect a child of the Epic. What behavior are you experiencing that is undesirable or unexpected? At the end of the day I expect it is working as it is designed. While stories linked to Epics are similar conceptually to sub-tasks of a story they…

what if you do the following search right after it is processed? createdDate >= 2019-06-21 ORDER BY createdDate desc any new issues should be at the top of the list. If it truly is not there then what I am wondering is if there are required fields for the project you are trying to create an issue for. If so then email will…

I was assuming Kier was on cloud. If so then falling back really isn't a viable option. If server then certainly that would be but at some point moving forward is inevitable I expect.

ah ok. you are on a starter license so the Community is your support channel. So when you go to your my.atlassian.com account what do you see? Maybe you wish to post a screenshot?

they should not by default. that is you can have stories that are not children of an Epic. If you are seeing stories under epics then they were added as such. Unless of course something has changed or broken. :-)

if you are the only person working the issue then you should simply have all issues assigned to you by default. Doing this, should result in you getting a notification as the Assignee. If you don't want them assigned to you then you can simply ensure you are in a group/role associated with Create notification.

check the Marketplace for addons for cloning projects. there may be something out there for NG by now too but not sure. You may have to reach out to the addon support channel to get the specific question on NG cloning answered.

agree. I created a PIT (projects for IT) where I collect non-project specific tasks and projects.

I would reach out to Atlassian Support if you are confident that the current SEN is indeed active.

so skipping past the "test", if you apply everything and send an email what happens? I assume the issue is not created? Does the email make it to the email inbox but not get processed?

I agree with the use of a separate custom field I would avoid using "Label" as it might get confused w/ Labels later. With Labels default filed you add new labels simply by entering them into any issue in any project. A space will indicate a new label so you can enter several at once, e.g. label-1 label-2 label-3. The…

that is a JQL query. If you want you can add more to it to meet your needs. Otherwise just paste that into the advanced search bar and see if it works.

you cannot control "where" info is placed but you can add custom fields to the card layout which will display on line-2. Just go to board settings > card layout.

@Rajni_Singla , i do not understand your question. It does not seem to apply to the original post at all. Maybe a new question/post is warranted?

Is this what you are looking for? fixVersion in unreleasedVersions() and status = Done

Components are project specific, i.e. not shared across projects. When an issue is created in a project the available components are those defined for that specific project. With that said, if you choose to make your components common, replicating them in multiple projects then you could certainly create a multi-project…

To the best of my knowledge you cannot. I would recommend providing feedback to Atlassian via the feedback link.

It isn’t possible natively but I believe there are addon options. You might look at extension-for-jira-service-desk

Yes but the key is in the process you use to “find” the issue. You can leave issue “unassigned” and display them in a Kanban or scrum board of us a dashboard.

JQL queries resolve to issues. You can include the sprint field as a column. project = xxx and sprint in openSprints()

You need to have admin permissions and the go to project settings > workflows, find and edit all workflows where you want to use the post function. On all transitions to Done you will want to add a post function to set “field value” then choose the Remaining Time field and the value of “0”.

You can find all documentation online at https://support.atlassian.com

use the Move function. if you are on cloud click on the ellipses in the top right of the detail issue view and select Move.

when you complete an issue and move to Done the remaining time should be set to 0. you can either remember to do this manually or you can use a post function in the workflow to set it to zero.