Build better products with our product team
Description - Add "Data Range" in the "Transfer Assets" process, along with all the other componentsWhy is this feature important to you - Because after the migration, the target use will own all the assets but is not able to change the custom data range used in the migrated workspaces projectHow would you like the feature to work - When the assets are migrated from a user to another, the migration includes also the custom Date Range.Current Behaviour - Currently there is the possibility to transfer all the assets from a user to another. The only components that are not migrated are Date Ranges.
This is something that should have come along to the NWE from Classic, but did not. The engineering team has said this is working as designed in NWE and support recommends an Innovation Lab idea at this point.How we found the issue... different users were seeing a different "Due Date" for the same task on the Team Requests page. Upon digging into it I found one user was seeing commit date, while the rest of us were seeing planned completion. Since everyone looking at the page has the same layout template, we were baffled.What engineering told us... Currently in NWE, on the Team Request page, the "Due On" date shows the planned completion date UNLESS there is a Commit Date, then the Commit Date shows. And there's no option to change this.Back in Classic, there was an option in the layout templates to select the "Due Date" as either Planned Completion or Commit date for both My Work (pre-Home) and Team Requests. But since My Work doesn't exist in NWE, that option didn't come along (even for Team Requests).Our use case... We sometimes have both a team and individuals (not on that team) assigned to the same task. If one of the individuals sets a commit date other than the planned completion date, the team requests page now shows that commit date to anyone who does not have a Classic layout template with Planned Completion chosen for the Due DateOur teams should always be working toward that Planned Completion Date, even if someone else assigned to the task wants to set a different commit date. If the project manager decides to update the task due date to that individual's commit date, then the team can now also work toward that new planned completion date.Next Discovery... if a user had a Classic layout template where Planned Completion was selected as the Due date for My Work and Team Requests, the Planned Completion date still shows as the Due Date for Team Requests in NWE.But... in the case where we discovered this, the user who was seeing Commit date was added to our instance after we switched to NWE, so they never had a layout template in Classic.Since we still have access to Classic for now, my concern is what will show on Team Requests for a Due Date once Classic doesn't exist anymore and we don't have the option of a workaround?
Description - Revert/discard an unpublished rule back to the live version Why is this feature important to you - Simpler/cleaner than copy/pasting the current live version back into the rule and preserves original modification dateHow would you like the feature to work - Menu option to discard last changeCurrent Behaviour - None, feature does not exist
We have numerous items (10s to 100s) with the same Planned Completion dates, but they bog down the calendar view. Is it possible to group on the day based on specific criteria? For instance, if I had 15 with the same Planned Completion Date and they are all a specific project custom form field, can I group and just have a single entry on the date saying something like "Specific Field (15)"? This would be wildly helpful for those of us with fewer planned completion dates and a ton more projects.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK