Build better products with our product team
Current status: when you build a multiple data blocks in the same Excel file using report builder, it can sometimes be difficult to distinguish between them. It is currently possible to group them based on metrics, dimension, or what sheet they're on. But if you have multiple data blocks with all the same components but just different date ranges, it's very difficult to tell them apart in the list of data blocks. How the feature should work: when making a data block there should be an option to give it a name. The ability to name data blocks will allow users to more easily distinguish between similar data blocks and make it easier to maintain their reports. Why this feature is important: the new report builder has been such a huge upgrade from the legacy version, but it can still be improved upon. Having named data blocks will make it easier when trying to maintain reports and share them with others.
Take information from Workfront planning to pull into WKFT core reports
Sometimes I get lost trying to figure out how to publish something in the New Email designer in Marketo – it seems like the button just isn’t there.After a while I realise there is one, but in a different spot and not outlined or coloured, so it just looks like some text.Then a few months later I get back to using Marketo and forget about it and have to hunt for it all over again.The publish button usually looks like the first image, but sometimes it’s somehwere else like in the second image. I have no idea what differentiates these two types and why there is a need for it to be different, and why these actions are included in a ‘summary’ and not ‘actions’ or similar.It seems like it would be better to keep them the same, or at least in the second screenshot give the buttons an outline so they actually look clickable and stand out more.
This is a Feature Enhancement request to add a collapsible Hamburger menu or similar for the various options for Asset Details in Assets UI. Currently a user has to hover over the button to figure out what the icon means. The same is applicable in order to view a datapoint quickly for example, Dynamic Media URL, for an approved asset.
Currently if a user is deactivated on workfront environment, user will still show as having access in admin console This is causing issues from a consistency point of view so data is accurate in both ends If you report on WF you will see less users active than if you report in admin console This requires us to do some manual batch updates on a regular basis to keep both systems consistentThe ask is that admin console and workfront instances are fully in sync so: Deactivating a user in Workfront removes or deactivates them in Admin Console Removing a user in Admin Console deactivates them in Workfront
The Problem:Right now, settings for New Issue Fields (like Planned Completion Date or Priority) can only be set at the Project level. This means every issue/request in that project shows the exact same fields.If I want to show the "Planned Completion Date" for one type of request (Queue Topic) but hide it for another to keep the form clean, I can't. It’s "all or nothing," which creates unnecessary clutter for users. Proposed Solution:Allow admins to customize field visibility at the Queue Topic level.Individual Control: Let us choose which native fields appear for each specific Queue Topic.Cleaner Forms: Requesters only see fields relevant to their specific request.Flexibility: Keep the Project-level settings as a default, but allow a "Topic-level override" for better customization.
In B2B marketing, brand consistency isn't a design preference, it's a growth lever. Every email, nurture stream, and interaction shapes how your organization shows up in market. But as content velocity increases, maintaining control over tone, terminology, and visual standards becomes exponentially harder. That's true whether your team is writing copy manually or leaning on AI to accelerate production. That's why we're excited to announce that Brands is now generally available in both Marketo Engage and Journey Optimizer B2B Edition to users with Admin level access. The Brand Challenge B2B marketers are expected to remember and apply every brand rule (naming conventions, tone of voice, required disclaimers, regional nuances - to name a few) across every email, every time. Add AI into the mix, and without structured guardrails, content can quietly drift: outdated product names slip through, tone shifts, terminology becomes inconsistent. The result? Manual review cycles, brand team bottlenecks, rework, and slower campaign execution. What Brands Does Brands lets you upload your brand guideline documentation directly into Marketo Engage or Journey Optimizer B2B Edition, where the functionality automatically extracts and structures: Tone and voice standards Terminology and naming conventions Required and restricted phrasing Messaging priorities Visual usage guidance This transforms a static document into a structured, AI-ready brand kit. Admins can refine, edit, and publish multiple brand kits which are each maintained as a separate entity. When creating content, marketers simply select the relevant brand, and governance is applied automatically within the workflow. No more referencing a 40-page doc. Critically, Brands works across both AI-generated and manually written content, so your entire email creation process is governed consistently, regardless of how copy originates. Introducing the Brand Alignment Score One of the standout features of Brands is the Brand Alignment Score. This real-time evaluation measures how compliant a given piece of copy is against your selected brand guidelines. It assesses dimensions like writing style and visual content standards, giving your team an at-a-glance signal of where content is on-brand and where it needs attention. Think of it as a live brand audit built directly into your creation workflow. Brands and Brand Themes: Better Together Brands works alongside Brand Themes to deliver unified governance across both copy and design: Brands govern what is said: tone, messaging rules, terminology, and phrasing Brand Themes govern how it looks: styling, fonts, colors, and layout Together, they eliminate the traditional disconnect between messaging approval and visual compliance, a common friction point in teams managing multiple stakeholders. Built for the Reality of B2B Whether you're a large enterprise managing multiple product portfolios and regions, or a smaller team without a dedicated brand function, Brands scales to your needs. Guidelines are enforced automatically during content creation, reducing dependency on manual review, shortening approval cycles, and increasing campaign velocity without compromising quality. For the Marketing Operations community, this is a meaningful step forward. Brand consistency is no longer dependent on memory or manual checks, it's embedded directly into your workflow, by default. Ready to get started? Explore Brands in Marketo Engage or Journey Optimizer B2B Edition today.
Export options are available for Issue Details screens, but nothing like this is available for the Updates section of an Issue. For auditing we show documented actions like system activity or comments made and the only option I have today is utilizing the print function which doesn’t allow viewing the entire page.
Description - Workfront Dark Mode Why is this feature important to you - Default Workfront is incredibly straining on the eyes How would you like the feature to work - Provide a black or dark background instead of white Current Behaviour - Non-existent
When we create projects, we would like it to be easily identifiable by a docket number, something sequential eg 17-xxxx and should increment only by the specific object type eg Project. Unfortunately, the only available autonumbering available on Workfront is through all objects, meaning if I have 2 projects created, this could be 17-ABX1 and 17-1257 because of all objects created in between. We need this number to be sequential to the object only.
Hi Everyone,I wanted to share a new Chrome extension I’ve been using called TagScanner that has significantly streamlined my Adobe Tags (Launch) auditing workflow.As implementation scale increases, keeping track of library bloat and rule dependencies can get tricky. TagScanner helps by loading all details about any Adobe Tags property directly from the page.Key Features:Direct Page Reading: It reads the Tags library directly from the browser—no remote code or extra permissions required. Comprehensive Visibility: Quickly view all active Rules, Data Elements, and Extensions in a single interface. Performance Insights: It displays exact file sizes and usage details, making it much easier to identify "heavy" rules or unused code that might be slowing down your site. Effortless Documentation: Perfect for cleaning up legacy properties or creating implementation documentation for stakeholders.It’s been a great addition to my toolkit for quick audits without having to dig through the Data Collection UI every time.Has anyone else tried it yet? I’d love to hear how you’re currently handling your implementation clean-ups or if you have any other "must-have" extension recommendations! Please find extension- https://chromewebstore.google.com/detail/tagscanner/mhejdbndckkddicchjjbaehfbmjjlmjn?utm_source=item-share-cb Thanks,Santosh Kumar
Marketo filters bot clicks based on IAB lists (known registry of non-human traffic sources/bots) or by identifying proximity patterns (multiple clicks within a short timeframe). However, bot activity has evolved leading to several bot engagements slipping through the cracks and firing off triggered smart campaigns that track link clicks. We recently identified two bot click behaviors we would like the development team at Marketo to investigate and patch: Logged clicks on links before “Email is Delivered” logging Click proximity outside the configurable 0-3 second window but within 30 seconds of email deliveryI am sure multiple Marketo Admins have dealt with false positive click engagements and have had to answer to their teams. This submitted idea within the Idea Portal is to alert the Adobe Marketo Engage development team of the need to tighten up criteria relating to bot click activity.
Managing campaign tracking in Adobe Analytics (AA) is often more complex than in Google Analytics. While GA relies on standard UTM parameters, Adobe Analytics utilizes the CID (Campaign ID)—typically captured via the v0 or s.campaign variable—to track the effectiveness of marketing efforts.Here is a guide on how to transition from manual tracking chaos to a streamlined workflow using UTMMind.Part 1: The Dilemma of Adobe Analytics CID ManagementFor many enterprise teams, managing CIDs is a significant operational hurdle. Without a dedicated system, organizations often face the following "Tracking Debt": Inconsistent Naming Conventions: One team might use fb for Facebook, while another uses facebook_ads or FB-Paid. This inconsistency shatters your reports, making it impossible to see a unified view of channel performance. The "Mapping Table" Nightmare: Since CIDs are often cryptic strings (e.g., em_promo_20240501), teams rely on massive Excel or Google Sheets to "map" these IDs to human-readable metadata (Campaign Name, Creative, Region). These sheets are prone to accidental deletions, version control issues, and lack of real-time access. Multi-Team Fragmentation: When Social, Search, Email, and Affiliate teams work in silos, they create their own tracking logic. Without a central "Source of Truth," the data in Adobe Analytics becomes a fragmented puzzle that analysts spend hours cleaning. Human Error: Typos, case-sensitivity issues (Paid vs. paid), and broken URLs lead to "unspecified" or "other" traffic in your reports, resulting in lost ROI insights. Part 2: Best Practices for CID CompositionTo solve the chaos, you need a structured architecture for your CIDs. Instead of random strings, a CID should be a delimited concatenation of variables.1. Define Your Variable StackA robust CID usually consists of 4 to 6 key dimensions separated by a delimiter (like an underscore _ or a pipe |). For example:[Channel]_[Sub-Channel]_[CampaignName]_[Placement]_[CampaignDate]2. Unified Naming Standards Always Lowercase: Prevent Facebook and facebook from appearing as two different line items. No Spaces: Use underscores (_) or hyphens (-) to ensure URL stability. Standardized Date Formats: Use YYYYMMDD for easy sorting. 3. Use Classification RulesBy using a consistent delimiter, you can use Adobe’s Classification Rule Builder to automatically split a single CID string into multiple dimensions (e.g., extracting "Social" into a "Marketing Channel" report) without manual uploading. Part 3: Solving the Chaos with UTMMindUTMMind transforms Adobe Analytics management from a manual chore into an automated, AI-driven workflow. Here is how it streamlines your tracking ecosystem:1. AI-Powered Template ManagementInstead of manually building complex Excel formulas to concatenate your CIDs, you can use the UTMMind Agent to set up your entire infrastructure in seconds. Simply provide a prompt, and the AI handles the heavy lifting.The "Magic" Prompt:"Create an Adobe Analytics CID Tracking Template (CID required only, remove all other parameters). The CID naming convention should be: [Channel]_[Sub-Channel]_[CampaignName]_[Placement]_[CampaignDate]. Create all required attributes, the template, and validation rules following Adobe Analytics best practices." UTM Agent:Attributes:Adobe Analytics Template:Naming Conversion Rules: How it works: Instant Architecture: The UTMMind Agent automatically creates the individual attributes (Channel, Sub-Channel, etc.) and binds them into a unified CID template. Dropdown Precision: When your team generates links, they simply select options from predefined dropdowns. No more typos, no more "creative" naming. Enforced Integrity: UTMMind creates Validation Rules that act as a "guardian" for your data. If a CID doesn't follow the naming convention, the system blocks it and triggers an alert. It’s impossible to "mess up" the tracking. 2. Frictionless Link CreationWhether you are launching a single post or a massive multi-channel campaign, UTMMind scales with you: AI or UI: Create links through an intuitive interface or simply ask the UTMMind Agent to generate them for you using natural language. Bulk Generation: Need 50 variations for a dynamic creative optimization (DCO) campaign? Generate them all in seconds. Just select the above Adobe Analytics CID Template and create you own tracking linkSingle Links Bulk Links 3. Seamless Team CollaborationTracking is a team sport. UTMMind allows you to invite teammates to co-work in a shared workspace. Stop passing around "Final_v3_Tracking_Sheet.xlsx." Share your template so that everyone uses the same "Adobe Analytics CID Template," ensuring cross-departmental alignment between Social, Search, and Display teams. Invite your teams into the workspace so that work togather 4. The "Single Source of Truth" (Audit Trails)UTMMind provides a searchable, permanent database of every CID ever created. Eliminate the Mystery: If an analyst spots an unfamiliar code like soc_ig_summersale_01 in Adobe Workspace, they can instantly search for it in UTMMind. Full Transparency: See exactly who created the link, when it was generated, and which specific creative asset it belongs to. This level of transparency ensures 100% data accountability across your organization. Manage and create your CID tracking specs is never easy as UTMMIND did. Free to Try yourself
Description - Many of my users work their tasks off of custom lists/reports/dashboards and not the Worklist. Currently delegated tasks do not pull into any sort of task/assignment reports, so I fear that if tasks are delegated to a user working off such a list, the tasks may fall off their radar as they don't pull in where their other assigned tasks do. Why is this feature important to you - Need this to fully utilize the task delegation feature. How would you like the feature to work - Fields would exist on task reports where you could pull in "tasks delegated to..." and it would reference user ID object. This would allow you to chose if you want delegated tasks to appear in a list or not. Even if they were a separate object report that would be ok! Just need some way to pull a them into a list. PS this is also an issue with personal tasks, reoccurring tasks, along with these delegated tasks. Though these are called "tasks" they don't pull into reports or show on the workload balancer. Meaning that we really cannot utilize these features as we otherwise would. Current Behavior - Delegated tasks do not function like regular tasks. You cannot pull a report of delegated tasks and they don't show in the workload balancer.
@tushargu@adobe.com @karmakar@adobe.com @carltonr@adobe.com Request for Feature Enhancement (RFE) Summary: Publish assets to the preview server Use-case: The requirement is to build an EDAM where all the assets reside. A key requirement for image management is the ability to expose an image for internal preview by other users/systems, without exposing the image publicly. Current/Experienced Behavior: Currently, there is no way to publish assets to the preview server for Assets customer. Improved/Expected Behavior: We would expect there to be an OOTB way to directly publish assets to the preview server. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager as a Cloud Service Customer-name/Organization name: Starbucks Screenshot (if applicable): Code package (if applicable):
Can Adobe implement the Google Feeback Loop system for Gmail:https://support.google.com/mail/answer/6254652?sjid=10186142268067450677-EU This is now out of Beta and is impacting all Marketo customers come Q1 2024 with the change in the Gmail spam rule changes:https://blog.google/products/gmail/gmail-security-authentication-spam-protection/
Request for Feature Enhancement (RFE) Summary: AEM Core components should have common and generic features, including accessibility. It appears that ARIA Attributes are not implemented in AEM Core ComponentsTeaser ComponentLooking at AEM's teaser component documentation, which showcases screenshots from author, the only accessibility field Adobe have is for the "alt" property.• Teaser Component (https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/wcm-components/teaser)When I look at Adobe example output (the Markup tabs under each section) and look at the sections with anchor links, I do not see any ARIA attributes either.• AEM Core Components - Example Output - Teaser Component (https://aemcomponents.dev/content/core-components-examples/library/core-content/teaser.html)Button ComponentOn the other hand, looking at AEM's button component documentation, Adobe DO provide an aria-label field for authoring.• Button Component (https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/wcm-components/button)When I look at Adobe example output and look at the anchor links here, I still do not see any ARIA attributes.• AEM Core Components - Example Output - Button Component (https://aemcomponents.dev/content/core-components-examples/library/core-content/button.html)My ConclusionI think that AEM put in the ARIA support for the button as a way to resolve common accessibility issues with HTML buttons, but Adobe has no broader solution for accessibility.I am requesting Adobe to add properties required for Accessibility to the AEM Core Components Use-case: Accessibility Current/Experienced Behavior: No capability to add ARIA Improved/Expected Behavior: Able to author ARIA label Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Lexmark, a Xerox Subsidiary Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enable log collection from Adobe Experience Manager (AEM) in Dynatrace as part of the monitoring integration Use-case: We have successfully integrated Dynatrace with Adobe Experience Manager (AEM) for performance and application monitoring. However, the current integration does not support log collection from AEM servers. Having the ability to collect and analyze logs directly within Dynatrace would significantly enhance our monitoring and troubleshooting capabilities. Current/Experienced Behavior: Dynatrace is integrated with AEM for monitoring, but logs from AEM servers are not being collected, as this feature is not supported. We previously created a support ticket about this, and we were advised that currently, there is no solution for log collection through Dynatrace in AEM Improved/Expected Behavior: We expect Dynatrace to support log collection from AEM servers, in addition to the existing monitoring features. This would allow us to have a more unified and efficient approach to monitoring and troubleshooting within Dynatrace Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 6.5.19.0 Customer-name/Organization name: BT ENTERPRISE Screenshot (if applicable): Code package (if applicable):
When building campaigns and journeys, teams often need on-brand visuals at the speed of iteration—without exporting work to disconnected design tools for every small change. Journey Optimizer’s AI Assistant for images, combined with Generative models under Brands, lets you choose how images are generated (default Adobe, partner, or custom Firefly models) and use prompts and settings directly in the content editor.This guide explains what generative models are in AJO, when to use them, where to configure them vs where authors use them, and pitfalls to avoid—so your team can roll this out safely and consistently.Official references: Create and manage generative models, Generate images with AI Assistant. When to use this patternUse Generative models + AI image generation when:You need new or refreshed imagery for email, web, landing pages, or push inside Journey Optimizer’s content editor, not only static uploads.You want brand-aware generation: authors pick a Brand, tune the prompt, and optionally use reference content so outputs stay closer to your guidelines.Your organization needs governance: central admins expose only approved backends (Adobe, partner, or custom Firefly models) via Brands → Generative models.You are ready to follow Adobe’s guardrails and user agreement for generative features (see “Common pitfalls” below). What you get: three model types (at a glance)Type Role (per product documentation) Adobe model Default Firefly Image Model 4—ready to use for general image generation without extra model setup. Partner model Gemini 2.5 Flash—positioned for specialized use cases. Custom models Brand-specific models trained on your assets in Firefly, then registered in AJO with a Model ID. Custom Firefly models require a Firefly ETLA agreement; see Adobe’s documentation for details. Part A — Where administrators configure generative modelsGoal: Decide which generation backends are available and register custom models.In Journey Optimizer, open Brands. Open the Generative models tab. Use filters (e.g. by Type or Status) and search to manage the list. To add a custom model: Add model → enter Name and Model ID (from Firefly—often from the Preview & test URL as customModelId=...) → optional Description → Test connection → Save. Use the advanced menu to enable or disable models as needed. Note: Only custom models can be deleted; built-in options are not removed the same way.After this, authors can pick these models from Image settings → Generative model when generating images in content. Part B — Where authors generate images (day-to-day)Goal: Create images inside a campaign or journey using AI Assistant.Create/configure your email, web page, landing page, or push delivery, then open the content or designer experience (e.g. Edit content, Edit web page, Open designer—see generative image for channel-specific steps). Select the asset or field you want to generate (for push, select Image as the field to generate). Open AI Assistant (or Show Content Assistant / Show AI Assistant depending on channel). Optionally enable Reference style and/or attach reference content (uploads or previously uploaded assets). Choose your Brand, write the Prompt, and expand Image settings—including Generative model, aspect ratio (where available), content type, visual intensity, color & tone, lighting, composition, etc. Click Generate, review variations, check Brand Alignment Score where offered, then Preview / Apply / Select as appropriate. For refinement, use options such as Generate Similar, Edit in Adobe Express, or Save—then complete your usual simulate, test profile, and review/activate steps for the channel. Example scenarios (quick)1. Default campaign imageryMarketing needs a fresh hero image for a promotional email. Author uses the Adobe model, sets aspect ratio, writes a short prompt, generates variations, and applies the best one—no custom model required.2. Strict brand look from owned assetsBrand team trains a custom Firefly model on approved photography. Admin registers the Model ID under Generative models. Authors select that custom model so generations stay closer to your visual system.3. Push with imageMobile team generates a push image field with the same prompt + Image settings pattern; Brands for push may be on a progressive rollout—confirm availability for your org. Common pitfallsPitfall What to do Skipping guardrails and legal Read Guardrails and Limitations and the Adobe DX Gen AI user agreement; involve your Adobe contact if needed. Expecting custom models without ETLA Custom Firefly training/registration is tied to Firefly ETLA—align with procurement/legal before promising timelines. Wrong Model ID Copy Model ID from Firefly Preview & test URL (customModelId=) and always run Test connection before Save. Assuming every channel is identical Web may use Show Content Assistant; push uses Show AI Assistant and explicit Image field—follow the channel section in the doc. Treating this as only “type text, get an image” Brand, reference content, and Image settings materially change results—prompt alone is rarely the whole story for on-brand work. ClosingGenerative models in Journey Optimizer are the administrative layer for which image engines your org uses; AI Assistant image generation is the authoring layer where prompts, brand, and settings become email, web, landing, and push visuals. Together they support faster, more governed creative workflows inside AJO—when your team is ready on policy, contracts, and training.
Request for Feature Enhancement (RFE) Summary: Determining the content of zip files solely from their title or file name can be challenging. It would be beneficial if marketers could attach images to the zip files (for thumbnails), as this would enable quicker visual identification. Use-case: Visually identifying the content of a ZIP via a thumbnail Current/Experienced Behavior: All zip files has same generic thumbnail. Thus, marketers need to check read through Titles/names. Improved/Expected Behavior: Associate Image with a ZIP to identify contents by looking at the thumbnail Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5/Cloud Customer-name/Organization name: Mondelez Screenshot (if applicable): Code package (if applicable):
The Text Field with Formatting is a great new display type that we'd love to convert a lot of our existing fields to. This display type can only be selected when creating a new field, so existing fields can't enjoy the benefits of text formatting.
DescriptionWe are using AJO to automate email, with email HTML being sourced dynamically via AJO Integrations(Beta) and Custom Actions from an external email creation platform (e.g. Stensul, Wordpress). Current workflow:An external team builds emails in Stensul. AJO then calls the Stensul API via AJO Integration (Beta) to retrieve fully rendered HTML, which is injected into an AJO email template and then sent in a Journey. We have also tried this process pulling content from Wordpress and have had success.This workflow functions correctly from a delivery perspective; however, we have identified a limitation related to link tracking and analytics. Observed LimitationChannel Configuration URL parameters and click tracking are correctly appended to links when emails are authored natively within AJO. However, links contained within externally sourced HTML (via Integrations) or URLs returned from Custom Actions are not rewritten by AJO at send time. As a result, these links do not receive tracking parameters, making click tracking and downstream analytics unavailable for these emails.Adobe Support has confirmed that this behavior is consistent with the current AJO design, as dynamically injected HTML and URLs returned by Custom Actions bypass AJO’s standard link‑processing pipeline. Why This Enhancement Is Important Automation and external content sourcing (e.g., Stensul, CMSs, design systems) are core components of modern enterprise email workflows. At the same time, analytics and click tracking are critical requirements for measuring campaign performance and overall business impact.The lack of automatic URL parameter appending introduces a gap between native AJO emails and integration‑driven emails, which limits adoption of automated and externally managed content at scale. Enhancement RequestSupport automatic URL parameter appending (or link rewriting) for the following content sources: HTML content injected into emails via AJO Integrations URLs returned from Custom Actions This capability could be opt‑in, configurable, or subject to validation rules. Enabling AJO to consistently apply Channel Configuration tracking parameters, regardless of content source, would significantly improve analytics support for automated enterprise workflows.
Hi Team,Is it possible to add "Executable Campaign" as a category in Campaign Inspector for better visibility?
Today: In the web UI, to create a new version of an existing asset, the uploaded file must have the same filename in the same folder. If the filename is different, AEM treats it as a new, separate asset, not as a version.Desired behaviour:New versions of an asset can be added regardless of the file name, e.g. by selecting the asset and clicking “add new version”.Reasoning:Updated files often come with new names but should still be stored as versions of existing assets. E.g. if a legacy asset was uploaded (or migrated from our old DAM) with the file name: coporate-presentation-2022-v1.ppt, I want to be able to upload a new version that is called hbk-coporate-presentation-2026.ppt We are not starting a DAM from scratch or renaming 30,000 files. That means that even though we can update to newer versions in AEM Assets, any errors, bad naming or typos in old file names get carried over into the new version. When users download the updated file, it has the file name of the first version, e.g. coporate-presentation-2022-v1.ppt, even though it is the 2026 version. That is confusing and unacceptable.
We'd like to have the option to apply contouring (i.e. edit the distribution of the allocated hours per day/week/month) to tasks & issues in the "Unassigned Work" section of WLB. The UI would be the same as that in the Assigned Work section. A task's resource needs fluctuate during the span of the task and it is often known before a user is assigned but can't be captured via the Workload Balancer UI at the moment. This would make resource planning easier and more real-life.
Already have an account? Login
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.
Sorry, our virus scanner detected that this file isn't safe to download.
