Jack Brickey Expert

So I’m confused here and want to step back. Why are you performing this bulk update? Why do you need to do it all at once? How often will this be done? Generally bulk edit is a rare activity. now that aside, yes if you associate all issuetypes to a single workflow it should work. Note that sub tasks I think must be done…

First, I don’t equate a story to a feature generally. A story is something that should be able to be completed within a sprint (~2wks). If your features are very small and can be completed within a sprint then ok. Now regarding your question, you definitely want to have individual issues for each user’s task. You might…

No that is not possible. If you attempt the Jira will split the disparate issues and ask that you choose which to change. Then you would need to repeat and do the other group of issues. 

You need a means of retrieving the number of linked issues whenever a new issue(s) is linked to an issue. I believe this is possible but have not attempted myself. here is a post that might help ~ Add-number-of-linked-issues-to-the-custom-field 

You can do this if: * You can construct a JQL to capture all of these issue AND * All of the issues share the same workflow

Are we talking about building in a kudos framework within the applications. If so, IMO, I don’t think kudos fits into the framework of learning software products. If you mean something else ignore the rest. In the context of educating users, I do think having some built in tutorials and more direct access to the…

Understood Trudy. I jumped right into that assumption based on what I read but assumptions can surely be a bad thing. 😜

Thanks John. I think Atlassian needs to test with iPads. I have run into a number of issues over the last year trying to admin using it.

Here is an article that references what aspects of the existing project will carryover to the new project. create-a-new-project 

Yes but getting there seems to be the trick in the recent changes. At least in my instance. I’m going to need to spend some time with new UI just to reeducate myself.

Gary, ultimately it seems you want to create a Jira software project using an existing project as a template. The challenge here, for me, is that there has been sweeping changes to the create project UI and my direct experience with this new UI is nonexistent. With that said, based upon what I observe, here is what I…

I see so you want the parent Summary field? I would probably look at automation and a custom text field.

It actually is displayed in the breadcrumbs…

If they don’t need to be customers on the service desk then yes remove them. However the reason you are directed to the portal I suspect is that you’re an admin. Only agents and admin‘s would be directed to the app. Customers will be sent to portal. Please keep in mind that if users are going to create issues in a JSM…

This seems odd. Is it a single user? I might suggest reaching out to Atlassian Support. 

I assume you have seen this - supported-versions-for-the-jira-cloud-migration-assistant 

Could you share an image that explains better what you’re referring to?

Hmmm, now that I think about it…if the User is a Customer of a JSM project then they will always be sent to the portal, not the app even if they have JSW access.

Nic will know if the following theory is possible or not… could it be that you deleted the user previously but left a number of issues that still had that users name associated to it, e.g. Assignee, reporter, watcher, etc.? This may have caused your current situation where you can’t add back that user email because it is…

Indeed! I always forget the empty part until I see the results 🙄

The error would indicate that you have not created any Epic yet. A roadmap consists of Epics and the underlying stories. Can you confirm whether you have created an epic as yet? If not click on the create and choose epic as the issue type. 

Are these customers currently users of Jira software possibly? You mentioned you added a test account was that test account new in your instance? There are a number of posts on email notifications in the Community that you might search and the following might help -…

Adding the following JQL snippet to your current filter AND (issue != apt-16 or “epic link” != apt-16)

What is “ETA”? Maybe this is a custom field? Depending on your project type and board type you may be able to add that field to your cards. If you have ellipses In the upper right of your board then click on those and select board settings - card layout and add the field to your card.

Great. Can you verify if there are two instances of the users in your system. That is do they show up in both Jira service management and in the user management section? next inspect the URL that is in the links and see if it’s pointing to the portal or if it points to the application. 

Yes sir indeed everything you create in the free version will simply still be there and work as normal in the paid version. Basically all you’re doing is attaching a credit card to your account they are by allowing you to expand beyond the free into the world of paid.

I feel your pain. IMO, This is one area that need some attention from Atlassian i.e. managing the commissioning/provisioning of customers. if you are working to migrate customers so that they can then use Zera then you should always use the “migrate to Atlassian account“ which can be found under User management - Jira…

Check to ensure: * project settings- customer notifications has invited enabled * the request didn’t go into spam box the first screen is used to manage what roles a user will have. For adding customers use the second screen.

For me to provide more meaningful input I guess I need more info on where you need help. However, I wonder if the following might be useful? 7-gadgets-for-a-powerful-Scrum-dashboard-in-Jira basically what I was suggesting above was to edit your current filter that is associated with the filter results gadget and add the…

No there is no way to add it and to be honest you shouldn’t need it since now all editing is done right in the current screen. There’s no need for a modal pop-up to edit field that already are being displayed in the detailed issue view.