Build better products with our product team
Ability to Change primary assignments on objects
Description - Provide an ability to move issues to ProjectsWhy is this feature important to you - It provides an adiditonal way to keep work movingHow would you like the feature to work - Exact same functionality available on webCurrent Behaviour - Functionality not available
Integrate Planned Hours and Actual Hours fields with the task/issue percentage complete bar and iteration burn down chart. This is important because it would show meaningful data metrics as opposed to hypothetical, relative, manually-set percentages complete. When the Planned Hours and Actual Hours fields are added to the task and issue cards, as the task and issue owners update the actual hours spent, the percentage complete bar is automatically updated based on the initial Planned Hours. Optimally, there would be 3 standard Agile task and issue fields to accurately show the effort against the work and to capacity plan:Planned HoursActual Hours SpentHours Remaining The current behavior relies on the task or issue owner to calculate the percentage complete based on what they think or feel.
Hi, it would be great if we could pull a similar report as the Email Link Click report, but for landing pages. so we could see the # of clicks on each link on our landing pages. We can currently pull one-by-one using smartlists, but it only shows the people we have in our Marketo system, not the gross # of clicks like we could see in an Email Link Click report.
Zusammenfassung der Funktionsverbesserungsanfrage (RFE): The expired assets predicate in the search filter currently only has one feature. Asset is already expired.Yet there are much more interesting things related to the expiry, that could be shown.Here are some examples for more interesting search filter regarding the expiry: Expired: The asset itself is expired(Ignore Dependencies) Has expired dependencies: The asset contains expired assets (Don't show expired assets, but instead those assets that contain an expired asset) Will expire: The asset will expire till (dateselect)+ usefull quickoptions: within the next 1 week, 1 month, 1year etc.)Be careful using those on sites / print projects that will be used for a longer period of time, since the printed media can't be "unpublished" but have to be destroyed, removed etc.) Will not expire: Show only assets that are free of an expiry restrictionI call it the "care free" option. Assetts can be used without having any fear that they will depublish themself / printed items do not have to be destroyed because one asset is no longer licensed Anwendungsfall: A user that wants to produce a print medium has to check if the assets that went into the print medium are not restricted with an expiry date. A cataloge might contain up to 800 assets. The cataloge will be printed with a circulation of 10k pieces. Currently, a user would have to check each individual asset to see whether it expires before the estimated time at which the print copies will be replaced by a newer one. Or a user builds an asset into a site, just to see that the asset depublished itself one week after the site launched because the expiry was overlooked. Aktuelles/erlebtes Verhalten: The expiry search predicate is built to make only visible what is already expired (what can not be used). In addition it makes it not easily distinguishable if the expiry flag is set because an asset itself is expired or if it contains a expired asset. Verbessertes/erwartetes Verhalten: Add additional functions as written in the RFE.Two checkboxes for expired, one for assets and another for dependenciesCheckboxes that look into the future and give the user a option to check if the asset will expire within a range or has an expiry at all. Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): 2023.8.13323.20230831T134651Z Name des Kunden/der Organisation: medi GmbH & Co. KG Screenshot (sofern zutreffend): Code-Paket (sofern zutreffend):
Request for Feature Enhancement (RFE) Summary: Support for multiple SMTP configurations Use-case: Many client work in multi-tenant set-up. Very often they need different SMTP configurations to send emails. Current/Experienced Behavior: Only one SMTP server can be configured by Day CQ mail service Improved/Expected Behavior: A factory configuration is available for SMTP configs. One can pick one dynamically and send emails Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Brillio Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Trigger dispatcher cache flush agent on receive in local AaaCS SDK Use-case: Developers needs the replication behavior similar to that of a server for validating caching use cases. Current/Experienced Behavior: An (enabled) Dispatcher flush agent is not trigger on receive events. Thus, .stat files are not touched and the caching behavior cannot be mimicked for entire flow Improved/Expected Behavior: Trigger dispatcher cache flush agent on receive in local AaaCS SDK Environment Details (AEM version/service pack, any other specifics if applicable): AaaCS local SDK Customer-name/Organization name: Brillio Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Extend Core components to display content from a linked CF Use-case: Many clients want to reuse content across multiple channels. Often recommendation is to use content fragments for authoring. However, being form-based, it cannot readily be used on a website. It would be good if we could extend core components such that they can display content from a linked CF Current/Experienced Behavior: CF being form-based cannot readily be used on web-pages Improved/Expected Behavior: Components should be able to pull content from a linked CF to display Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.x & AaaCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Rollback feature for Production Deployment Use-case: Feature request for Cloud manager, where a process in place where we click on one button and confirm to roll back the code which was deployed to production. Current/Experienced Behavior: No efficient process to rollback in AEM production environment Improved/Expected Behavior: Functionality that allows AEM users to roll back to a previous version in production environments Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Providing advance notifications and implementing a code validation pipeline for upcoming CM rule updates would be highly beneficial, as it can help mitigate unexpected pipeline failures, such as the one mentioned in the provided link. Use-case: Failed pipelines due to sudden CM rule updates Current/Experienced Behavior: Pipelines suddenly start failing if they don't comply to CM rules Improved/Expected Behavior: A prior notification and separate pipeline to validate code against upcoming updates Environment Details (AEM version/service pack, any other specifics if applicable): AEM instances using Cloud manager Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Should have leverage to provide required permissions like (Read, Modify and Delete) from touch UI for Experience fragments folder. Use-case: Current/Experienced Behavior: In order to get inherit Edit permission Adode team has suggest to provide jcr:all permissions for the Experience fragment folder. Improved/Expected Behavior: We need to leverage in such a way that we can provide required permissions like (Read, Modify and Delete) from touch UI. Environment Details (AEM version/service pack, any other specifics if applicable): Version : Adobe Experience Manager (6.5.14.0) Customer-name/Organization name: American Express. Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Extend Adobe Sensei capabilities in AEM Sites to extend capabilties of content creation and smart tagging Use-case: 1. Auto/smart tag webpages 2. Add description/title (for SEO) 3. Content curation Current/Experienced Behavior: Currently only content summary for CF using Sensei is supported Improved/Expected Behavior: Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description - With the new functionality for "Enable faster Workfront release cycles," it would be ideal to have the ability to opt into the fast release in lower environment(s), but keep the quarterly release in your Production environment.Why is this feature important to you - For new feature testing purposes, to offer feedback to Workfront, and more time for planning of communications to end users.How would you like the feature to work - Similar to how it works for Production; if the checkbox for the "Enable fast release process" is checked, in a lower environment then it should allow for the install of the new release functionality to be installed during the next release in that respective lower environment. If not checked, then the quarterly cadence of release would follow.Current Behaviour - There is no way to opt in to the fast release cycle in SB01 or SB02, but keep the Production environment in the Quarterly Release cycle.
アンケート回答や問い合わせ内容を格納する際にPMCFをフォームで使用する機会は皆様多いかと思います。 便利なPMCFですが、プログラムのメンバタブでしか確認できません。 Marketoにはスマートリストの定期配信という素敵な機能があります。しかしPMCFはスマートリストの表示項目として選べません。 問い合わせ内容を関係者に定期配信で連絡できれば、省力化にもなりリードへのフォロー漏れを防止できます。 Marketoの仕様としてすぐに実現は難しいかもしれませんが、 将来のアップデートでこの機能がサポートされることを強く希望します。
The Campaign Queue can be an important indicator of system health. Since excessive volume in the queue can be an indicator of critical issues such as long delays in Syncing or processes completing out of the expected order, timely awareness is important. However, it is not always convenient or possible to view/refresh the Campaign Queue at all times of the day. It would be great if there were Notifications for the Campaign Queue for excessive volume or delays. This could be the number of campaigns, number of leads in a campaign or total number of leads currently backlogged. To deal with the different needs and activity levels of various clients, the notifiction could be based on user set thresholds.In general, it's always a good idea to keep an eye on the Campaign Queue when testing and activating new campaigns. However, sometimes an excessive backlog can develop due to things out of your control and knowledge. An automated alert would be good for those cases.We recently had an experience where happened to notice that Campaign Queue was much larger than normal, and growing. We have a lead processing campaign with a wait step to allow scoring and other data management campaigns needed for proper routing to fire before syncing the lead to SFDC. We saw leads synced before they were scored, etc. even when the sync was delayed hours. Unfortunately, this had been an issue for over a day before we discovered it.Here are some other ideas for enhanced monitoring features for the Campaign Queue. I've included the links if you want to "like" them, too:https://community.marketo.com/MarketoIdeaDetail?id=08750000000ITqHAAWhttps://community.marketo.com/MarketoIdeaDetail?id=08750000000IQNCAA4Thanks,Jason
Often we need to import a series of different lists, we would like a view with the following to the lead database.1. List of all imports with the name of the file, date and time, and results (leads updated and new leads).2. For in process imports, a status (i.e. in process, importing, completed).Some imports don't work, so it would be ideal to get a status message back on what is the cause (i.e field format, etc).
At the moment it is only possible to manage Person records in the Marketo UI and to some degree also Company records. That means that anything else needs to be handled via CRM or the (especially with custom integrations) via the API. I am fully onboard with not allowing any marketing user to freely make any more changes to the database. There is however a use case for managing some data via the Admin screen of the UI, so the need for development resources becomes less. Some topics where this would be interesting: Deleting Company records that are orphaned (no contacts, opportunities, custom objects associated anymore). Deleting Opportunity records that are orphaned (no opportunity role or company links anymore). Deleting historical data in Custom Objects. Any other use cases you can see?
When building a template it would be nice if there was a way to lock/unlock mktoList values. Our templates are coded so our marketers have all the tools needed to build an email or landing page, stay on brand and not need to know code. A great feature we use to do this is mktoList values. We enter values so they have a set list to choose from. Recently we discovered that even with a set list, someone can still change the value using the input field. For example, adding something like the image size lock to the mktoList would be a nice option as it would help avoid possible human error or a missed QA and could be turned on or off.Something like: mktoLockList="true/false"
Currently, when multiple records are merged, the most recent date of the New Person activity is presented as the Created date for the newly merged record. This gives an inaccuarte "age" for the record, and implies that the email address has not existed within Marketo as long as it has. The shared history of the merged record can be seen - with both New Person activities - but should not the Created match the date the email was originally created in the database? The issue can best be seen when pulling a SmartList based on the "Person was created" filter and either the "On or before"/"On or after" conditions. Sort the Created column, and notice values outside the given condition.
A coworker has requested a custom form containing several custom fields,each with multiple checkboxes in a single row within a custom form,to look like this: Check all that apply:Category #1: ☒ Historical Reports ☒ Historical Graphs ☒ Scorecard ☒ My DashboardCategory #2: ☐ Historical Reports ☐ Historical Graphs ☐ Scorecard ☐ My Dashboard He has also specified a radio button field with five options.They should be displayed thusly: Tomcat Constellation Tornado Hustler[and your pathetic page has mishandled the radio buttons!] In the implementation of this, Workfront displays them one button per row,resulting in this: Tomcat Constellation Tornado Hustler[Again, the radio buttons have been mishandled by your page.] These horizontal layouts are much more readable and is less wasteful of vertical space,since the current default behavior allows only one checkbox or button per row. Please add this capability!
Our marketing team all valued a previous feature that has now been discontinued - this was the ability to tick a box on document proof updates that added everyone tagged as approvers "Ask for Approval" - it was a fast and easy way to provide our stakeholders with updates on the documents and have them added as approversWhy is this feature important to you -Saved us time - was easy and quick to use
Description - Create the ability to customize the Groupings of Tasks / Issues on Boards Why is this feature important to you - We track work by Iterations and it would be helpful on the Boards feature to group work by Iteration, or even display/group work by portfolio. The current options are too limiting How would you like the feature to work - Provide the ability to create customs Groups- similar to the Group feature on reports Current Behaviour - The only grouping options today are Assignee, Tags, None
Description - Allow a text or number field to have specified field formatting, such as phone number ### - ### - #### or allow input of numbers being between value 1 and 100Why is this feature important to you - Makes data entry less prone to errors but allows you not to have to enter all the possible values in radio buttons or dropdown fieldsHow would you like the feature to work - On custom form on text and number fields have additional button that allows logic to be added and formatting. This would need to then be carried forward to reporting so display the values correctly too (including in textmode new valueformat allowing for the mask to be added)Current Behaviour - If its text its text, if its a number its any number
This is edited since they already had the original idea in the works.Description: The "new"-er idea is to allow for a consolidated Kanban view for Tasks and Issues in a single list.It's important because: Since most users don't care about whether the "thing I gotta do" started out as a task or an issue, it would be beneficial to see them all in one list. It's so much easier to prioritise and organise when you can see everything together.How I'd like it to work: a choice on the board itself or in the project nav bar to include Tasks and Issues together. Or, make that the default and add an indicator on the card telling if it's a task or issue.How it works Now: Users have to go 2 different places to see tasks and issues even on the same project Old-er original idea:Description - Put a "Boards" view icon on the Issues page of projects.Why is this feature important to you - A lot of organisations use issues extensively in projects. Also this would be great for request queues.How would you like the feature to work - Exactly that same as the Boards view for tasksCurrent Behaviour - You have to create an external Board and filter for the issues in the project you want to target.
Would love the capability to simply transfer hours from one project to another. For instance, if hours were logged to a project that is then split into 2 projects, would like to copy/move the hours when copying/moving the tasks to the new project. We do report on hours per client per quarter/month, we need to make sure we have the right hours logged to the right project/client on the correct dates. Which sometimes requires modifying how the project from original setup.It would be amazing to have a checkbox alongside the other checkboxes (Constraint, Assignments, etc.) that pop up when you copy/move tasks. This checkbox could labeled "Hours". Another solution could be: within the Hours section of a task or project, the ability to check the hours you want to move and click "Move to" from a dropdown or similar.Currently I have to log in as the user who logged the hours, remove the hours they logged from the original project, then go to the new project and log the hours to the specific tasks on the specific dates. It works, but it is pretty manual and time intensive.I have seen a few other articles regarding this feature also but was encouraged to create a new idea, since these were a bit older. Transfer Hours from one task/project to another?Making hours portable between projectsThank you!
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
