Jack Brickey Expert

Can you share your solution here?

Hi @Mike.Mather , there isn't a means of rotating a table n Confluence at least OOTB.

There isn't a means of doing this that I can find.

@Kelly Addison , I'm not sure what to do with this Community post. Can you elaborate if there is a question you need assistance with?

Are you an administrator? If so please go to project settings > screens and find your screen scheme. Click the pencil to edit the scheme. You will need to add Epic name to your Epic create scheme. Note if this is a shared scheme it is possible that someone removed the Epic name for a reason.

is she a project admin still? if so, and the workflow isn't shared across projects, she will be able to edit.

i have a custom field for Facility. you can certainly create a Location field (single select).

i am not familiar with stories/label gadget, please share more on this. Personally I would move away from labels. for this UC you need a single select field so you can control the selection. Labels can include more than one option and even misspellings.

You can recreate the project in the new instance, export the issues and import using CSV My advice is to work with a few test issues first to get the import the way you want and save the import config file to complete the task.

but if you click on the more details what info is provided? I expect a condition is not passing

also... It may be obvious, but you need to ensure that your "Done" status is in fact mapped to the right-most column of your board.

Disclaimer: I am just now learning forms myself. Based on earlier reading, my assumption is that you can add Jira fields to your forms. So I'm assuming that you could include the Jira attachment field to your form and you could update your workflow to require an attachment on the desired transition including the create.…

Disclaimer: I am on standard and I have not tried advanced roadmaps. It is my understanding that roadmaps in standard for CMP are equivalent to roadmaps in TMP projects. Moreover these roadmaps are not the same as advance roadmaps in premium.

Hi @Steven Lees-Smith , so if I understand you correctly it seems that your current process is to move a JSM issue over to a JSW project if it requires development. Is that correct? Assuming the above is correct, I would highly recommend a different process. This is fairly common usage throughout the community so not just…

if you wish to restrict to a single issue type within a project you will need to leverage Issue how many albums yeahSecurity as well as the project permissions. I would recommend you familiarize yourself with the following documentation: how-do-jira-permissions-work configuring-issue-level-security 

@Simon H , so I see Forms in JWM today directly w/in the project screen (not admin) and am playing around with it now. So, when Forms is available for JSM will it be the same? Also, will Forms be added to JSW projects?

@saulmb.7 You are in the wrong place. 

No this is not possible. Maybe you could leverage Automation to set the Assignee?

you may want to also give them Schedule Issues permissions.

could it be that you are are on the old editor? Are you able to enter "/code snippet" or do you need to click on the "+" and select "code block"?

There is a lot of good docs. I would suggest you go here and search for your topic JSW - https://support.atlassian.com/jira-software-cloud/resources/ JSM - https://support.atlassian.com/jira-service-management-cloud/resources/ 

i might. sometimes the import, once you have a working config file, can be easier. hard to say which way to go w/o experiencing the environment firsthand. it is going to be tedious either way.

It really isn't that bad unless you have a lot of projects abd custom fields that you need to retain. The way I would probably do this is: * stand up the new projects as required to move forward. Keep in mind that many of the fields or capabilities of JSM won't reply in JSW or JWM, e.g SLA, Request Participants, etc * Use…

Hi @Sravani Battu , you cannot migrate a project to a different template. You can modify your existing project to mirror the desired template or configuration. How much work this would be depends entirely upon where you're starting and where you're going.

so is Premium tier out of the question? If not then this would offer asset management through Insights.

LOL...i'm just waiting on my admin creds to @John Funk 's instance. ;-) @Martin Doucet , you definitely should move all issues from JSM to JSW/JWM projects. 

what do you want to do with the data? if you want to be able to work issues then Move issues to a JWM/JSW project. If you dont need then just export to Excel or maybe create a free Cloud instance.

Component Lead not yet supported - AUT-917 - Components smart value should include description & component lead I am wondering if using a cascading custom field might work? It seems if approval is a step in the process maybe incorporating a sub-task would be a good idea?

Hi Rose, you can't illustrate "sum" within the JQL capabilities. There are possible solutions leveraging Automation and custom fields in some scenarios. you might consider exporting to Excel or some addons, like EasyBI.

it sounds like you are looking for where the Reporter != Assignee. Is that correct? Unfortunately JQL doesn't support that OOTB. You might be able to leverage automation and custom fields to achieve your goal. Or consider a scripting add-on.